Uncheck "predict network actions to improve page load performance".Open the settings in chrome chrome://settings/.I have covered the topic previously, check out the link for detailed instructions:
You can move data back into the default folder but need to understand that this may bring back the issue that you are experiencing.Ĭonnection errors may also be caused by Chrome's DNS prefetching. It creates a new default profile folder that is used from that moment on. Rename the default folder to default.backup and restart Chrome afterwards. To create a new user profile, close Chrome and open the profile folder on your local system. This includes bookmarks, extensions and settings that you may have changed in Chrome.
You can create a new profile, but if you do, custom data won't be available by default. Open chrome://extensions/ to do so.Īnother option is a corrupt profile. I suggest you disable extensions one by one then to see which is causing the issue. If you can load it in private browsing mode but not in the normal mode, then an extension or script is likely interfering with the connection. If you can, try to load it again in your normal browser window. Open a new Incognito window with Ctrl-Shift-N and try to load the web page that threw the Aw, Snap error to see if you can load it. Why? Because extensions and scripts do not run in it by default. One of the easiest options to find out is start the browser in incognito mode. If you can open other websites but not this one, check your user scripts and extensions to see if they may block access to the site in question. If you wanted to open a page on it, try the homepage instead to see if it is available. First unrelated websites, for instance and if that is possible to another page on the same domain you tried to connect to. The first thing you may want to do is check if you can connect to other websites. Google has created a support page that lists four solutions to resolve the site loading error when you receive it frequently in the browser.
0 kommentar(er)
