In this example, the Aw, Snap message is displayed with Salesforce.
The Aw, Snap error appears due to some memory issue with Chrome. Pressing Shift + Esc in Chrome will open Chrome's Task Manager, and display the amount of memory being used by Chrome. In the screen shot below, Chrome is using a total of 414,092K of memory.
The follow recommendation should reduce the amount of memory required to run Chrome, and may prevent Chrome from producing the Aw, Snap error.
Clear the web browsers history.
Remove unnecessary extensions from Chrome.
- Near the upper right-hand corner of Chrome, select the three dots icon > Settings.
- On the left, select About. Chrome will automatically check if there's an update available.
Close unnecessary tabs
If there are many tabs open in Chrome, this may cause Chrome to run out of memory, and then crash. Close unnecessary tabs.
Chrome Cleanup Tool
Download, install, and run the Chrome Cleanup Tool - https://www.google.com/chrome/cleanup-tool/.
If the issue persists, repair Chrome.
If the issue is very persistent, impacting the ability to use Chrome, restart the PC. This is not a long term solution, and only meant to fix cases where Chrome is constantly producing the Aw, Snap error.
Enable logging in Chrome
- In Chrome, select Settings.
- Select Show advanced settings.
- Tick Automatically send usage statistics and crash reports to Google.
- Close all open instances of Chrome.
- Select the Windows Start icon, type Chrome in search, right-click on the Chrome icon and select Properties.
- Appened --enable-logging --v=1 to the end of the Target (example: "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --enable-logging --v=1)
Note: --v=1 is verbose level 1.
To view the log:
- Launch Chrome.
- Open chrome://crashes in a new tab.
- When chrome produces the Aw, Snap error, a crash ID will be displayed at chrome://crashes. In this example, the Crash ID is 486940d9-f5a5-40b6-a0e7-48237af69f81.
- To view the log with the details of the crash, open the C:\Users\A299JJC\AppData\Local\Google\Chrome\User Data\chrome_debug.log in Notepad.