Sometimes you will find yourself in such a position, that either after you have just installed your Google Chrome Browser or while you browse, you will get this annoying error saying “Aw, Snap!” along with some other error line which says that something went wrong while displaying the page, a typical Aw Snap Google Chrome problem. This line also recommends to reload the page as a solution provided on spot.
So first thing you should do when you get such an error is to reload the page, maybe it’s just a simple loss of communication or the server returned an output which is something else than what the browser was expecting.
If this fails to give any results, you will have to try one by one the following possible solutions:
1. Check your anti-virus and firewall applications.Here you will have to check two things: – first that your computer’s firewall or anti-virus is not messing with your browser.There are reported cases when Symantec Endpoint Protection, Comodo firewall and Mcafee can cause some of your Google Chrome issues; in such cases you will get this error random on a daily basis. There might be other faulty software too which could impact your browser, so do not think if you are not using the ones i mentioned, this does not apply to you. Try to disable these programs while doing a short test running Google Chrome. If the browser is working, you will have to add a rule to the security software that used to trust this application and not block it’s content. You will probably have to re-enable the software before adding Google Chrome to trusted applications. – second thing you should consider is malware on your computer, so update your security software and scan for threats.Fix them if you find anyand then retry the website which wasn’t loading before with your Google Chrome. You can find a post on this website with ways to protect your computer against security threats, and how to prevent malware from infecting your PC. 2. Check your Google Chrome extensions. Click the wrench icon on the browser toolbar – select Tools. – select Extensions. – On the Extensions page, click Disable on the extension you would like to deactivate. You will have to do this one by one or backwards, disable all of them and activate them one by one, until you find the one who was causing this. This doesn’t mean one of them is the culprit for sure, it might not be any of them and you will have to go to the third possible solution below. You will have to refresh the webpage after you have done any of the above modifications, regarding enabling/disabling extensions, in order to see the change. 3. If you still have the problem, it means Google Chrome’s user profile might be corrupted. To create a new userprofile follow below steps: – Close Google Chrome – Locate Google Chrome “Default” folder (this is the folder that also stores your bookmarks, cache, cookies, history – so you might want to copy some from the old default folder we are going to rename now to the new created default folder after you start Google Chrome again – I think this would be best for at least your bookmarks). You can reach the folder’s usual location by checking one of below paths, depending on your operating system: Windows XP: %USERPROFILE%\Local Settings\Application Data\Google\Chrome\User Data\ Windows Vista and Windows 7: %LOCALAPPDATA%\Google\Chrome\User Data\ Mac OS X: ~/Library/Application Support/Google/Chrome/Default Linux: ~/.config/google-chrome/Default – Rename the folder “Default” to “Default_old” without the quotes. It can also have another name, I just like using _old when needed, it’s like an agreement for me: I started to work this way, I stay this way. Probably you will create your own or youcan use mine, what really counts is to have Default folder named to anything else so another Default can be created by Google Chrome when you start the browser. – Open Google Chrome (I assume you followed my request and closed it as I said in first step so we may re-open it now). This will create a new Default folder with a new Google Chrome user profile.
If you are still having the problem with all this done, there is one more solution, the ultimate one that will really work. I also left it as the last one as it is not the best thing to do. This would be more for testing purposes so you know there is not something really wrong with your computer but it is not recommended and I don’t encourage you to let it set forever with the idea of using it like this. It should be more like a work-around until we can find something else. That’s why if it worked with this one, but it didn’t with the above solutions, please leave a comment with the error code you can see in your event viewer and we will treat each problem based on the error code.
What is the actual mysterious solution ?
Right click on Google Chrome shortcut on desktop.
In the “Google Chrome Properties” window that opens, at the end of the text box for “Target” field put a space after “chrome.exe” and add this code:
–no-sandbox
So it should look something like this:
And the code in your target field should be something like this:
“C:\Documents and Settings\Your_Username\Local Settings\Application Data\Google\Chrome\Application\chrome.exe” –no-sandbox
Don’t forget to click on Apply and then Ok and you are set, you can also try a website and you should see the error is gone.
How to get error code ?
Go to Start – run – type “compmgmt.msc” without the quotes, press enter. Then go to “Event Viewer” – select Application – and you will have to scroll down until you find the error code associated with your event listed in there for your Google Chrome error. To open an event in that list, you will have to double click on it.
With this being said let me remind you what this option actually does if set: it will disable the low privilege sandbox for showing web pages, in other words, leaves your computer vulnerable to flaws, security exploits like back-doors that could be installed from those web-pages on your system without even knowing. This is even more dangerous when you are browsing a lot and like any Internet user, you will never know what it is there waiting for you.
I hope you will follow my advices. As for the last solution provided, I encourage you to give me the error codes so I can treat your problem accordingly and so you can avoid using Google Chrome with sandbox disabled on a daily basis.
VN:F [1.9.22_1171]
please wait... Rating: 3.0/ 5 (10 votes cast)
How to fix "Aw, Snap!" error - Google Chrome problem, 3.0 out of 5 based on 10 ratings