I studied this related question, but am still stumped.
I have an application that periodically shows the "Aw, Snap!" error screen, and to debug it, I have:
- Launched Chrome with verbose logging enabled
- Caused the tab to crash
- Found the debug file (on Mac, ~/Library/Application Support/Google/Chrome/chrome_debug.log)
- Examined the file for informative errors
But I haven't been able to find anything pertinent to the crash. Which is surprising. I expected some prominent ERROR level log entry with lots of details.
What would I expect to see in the log for an "Aw, Snap!" tab crash? Am I even looking in the right place? If not, where can I get crash details?
51 Answer
If no error is found in the log file while running with logging (--enable-logging --v=1), try to run Chrome from the command-line, sometimes it should show more.
On macOS to display logs from Chrome, you can run this command:
log stream --level debug --predicate 'processImagePath contains "Google"'or by running Console app. If no error is shown, check for any crash dumps (location should be printed in the log). In Console app, crash files can be found under User Reports section (or directly in ~/Library/Logs/DiagnosticReports folder).
If you found related Chrome crash file, check which Thread crashed and find its stack trace, which can point to the cause.
If stack trace consists only memory addresses, you've two possibilities:
- Report the problem at Chrome bug tracking system including your uploaded local crash report ID (see:
chrome://crashes/), so they can be translated by Chrome maintainers using debug symbols. - Compile Chrome from the source (takes a long time), then run directly from the Terminal. After that, each “Aw, Snap!” error should be followed by the full stack trace including functions and line in the source code file where it happened.
See also:
- Chromium - How to enable logging?
- How to determine what is causing Chrome to show the "Aw, Snap" dialogue
- How to get more info when the “Aw Snap” screen shows up in Chrome?
