Troubleshoot Chrome crashes
Crashing issues with Chrome or a Chrome device can be caused a number of things. Here are some potential issues you might encounter:
Aw, Snap! error message
This error message occurs when a webpage doesn't display correctly.
In most cases, you can reload the page to dismiss this error. If you keep seeing the message, try closing other webpages that are open or restarting your device.
If you continue to have problems see Further troubleshooting.
Page unresponsive box
You might see this error when a particular webpage or set of pages cause a problem.
To fix the problem, select the webpages in the box and click Kill pages. Then, reload the pages. If you still see the error, try restarting your device. If you continue to have problems, see Further troubleshooting.
Hanging tabs
When a tab hangs, it usually appears as a white page that is stuck loading. The title of the affected tab is Loading and it has a spinning icon.
This issue usually means there's a graphics rendering issue. Sometimes, opening a new tab and browsing to another page can help the affected tab to load. If this doesn't help, try restarting Chrome or your device. For more information, see Further troubleshooting.
Chrome device crashes
If the entire Chrome device locks or freezes, the problem may be more serious. We recommend that you look at the Chrome device debug logs and use Log Analyzer to examine them.
Further troubleshooting
If you continue to experience crashing issues, we recommend the following:
- For Chrome devices, try to diagnose the issue by collecting Chrome device debug logs and using Log Analyzer.
- For browser issues, try to diagnose the issue by collecting Chrome browser debug logs.
- If crash reporting is enabled, browse to chrome://crashes to find the crash IDs and file a bug.
- If you have problems with Chrome on a Microsoft® Windows® device, use Windows Process Explorer logs to gather details about how Chrome interacts with Windows.