How to get more info when the "Aw Snap" screen shows up in Chrome?

Debugging Problem Overview

I am trying to view a page in Google Chrome, but I get the message: "Aw, Snap! Something went wrong while displaying this web page". Is there a way to get more information about what went wrong?

Update: the "Aw, Snap" remark is shown only when the JavaScript console is visible.

Debugging Solutions

Solution 1 - Debugging

First enable Automatically send some system information and page content to Google to help detect dangerous apps and sites from Settings -->> Advanced -->> Privacy and Security

then enable Crash reporting in Chrome as below

Open chrome://crashes
If it shows crash report as disabled, enable it. If crash happens it will dump the crash report at C:\Users\{username}\AppData\Local\Google\CrashReports

This would give more info when the aw snap screen shows up in chrome

Solution 2 - Debugging

I don't know if you'll see much in the non-debug build but try turning on logging and see what shows up:

Launch Chrome with these flags: --enable-logging --log-level=0

On Vista your log file would be in: C:\Users\<username>\AppData\Local\Google\Chrome\User Data\Default

On XP your log file would be in: C:\Documents and Settings\<username>\Local Settings\Application Data\Google\Chrome\User Data\Default

See http://www.chromium.org/for-testers/enable-logging for details.

Solution 3 - Debugging

When you run DevTools on the website which is about to crash, it may give you some clues.

For example, when the tab will hit out-of-memory limits, the debugger will pause the code just before the crash (Chrome, Opera, etc.). The memory usage can be checked in the Memory tab.

If the cause is different, run Chrome from the command-line with --enable-logging --v=1 and check the logs (system logs and chrome_debug.log file).

macOS

If you're on macOS, such crashes should be automatically reported. They can be checked in Console app and check for Crash Reports. Or find them in Finder, the files are located in /Library/Logs/DiagnosticReports (system-wide) and ~/Library/Logs/DiagnosticReports (user).

Check also Chrome logs in real-time, by:

log stream --level debug --predicate 'processImagePath contains "Google"'

Linux

For Linux, check: <https://stackoverflow.com/q/17965/55075>

Solution 4 - Debugging

I faced the same problem in chrome, I was using it at Ubuntu operating system, I just update chrome and restart my system and its working fine!

Solution 5 - Debugging

Get a Chrome crash dump (see other answers and a search engine for most up-to-date methods for that) and you can open it in a debugger.

Memory-related issues are usually pretty obvious, like if the heap is overflowing or not being compacted fast enough for new objects to be added. Chrome will try to save itself from crashing by detecting whether the GC was ineffective at marking sufficient things for collection / compaction - "CheckIneffectiveMarkCompact" and "FatalProcessOutOfMemory" where the GC is basically thrashing trying to reclaim memory over and over, but not able to do so. This is usually a sign of "bad" javascript - not necessarily bugs, but design flaws such as loading too many records from an API into memory at once, such as when rendering long lists of data or features on a map. Depending on the device where Chrome is running, it can easily be overtaken and will shut down the site/tab with the "Aw Snap" error.

    #endif  // V8_FUZZILLI
    } else {
      fatal_callback(location,
                     is_heap_oom
                         ? "Allocation failed - JavaScript heap out of memory"
                         : "Allocation failed - process out of memory");
    }

Solution 6 - Debugging

After chrome update my chrome browser was stopped working, So below fix I have applied for time being You can disable sandbox mode by following below 2 ways

either you can run below command "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --no-sandbox

or if you have admin rights you can update registry

REG ADD "HKLM\Software\Policies\Google\Chrome" /v RendererCodeIntegrityEnabled /t REG_DWORD /d 0

Solution 7 - Debugging

That page means that something inside the browser went wrong, so maybe run the browser under a debugger?

Content Type	Original Author	Original Content on Stackoverflow
Question	Dimitri C.	View Question on Stackoverflow
Solution 1 - Debugging	Tarun	View Answer on Stackoverflow
Solution 2 - Debugging	Pierre-Antoine LaFayette	View Answer on Stackoverflow
Solution 3 - Debugging	kenorb	View Answer on Stackoverflow
Solution 4 - Debugging	Ashwani Panwar	View Answer on Stackoverflow
Solution 5 - Debugging	nothingisnecessary	View Answer on Stackoverflow
Solution 6 - Debugging	Manoj Patil	View Answer on Stackoverflow
Solution 7 - Debugging	user181548	View Answer on Stackoverflow