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.
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
This would give more info when the aw snap screen shows up in chrome
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.
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).
Related:
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"'
See also:
For Linux, check: How to generate a core dump in Linux when a process gets a segmentation fault?
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!
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");
}
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
That page means that something inside the browser went wrong, so maybe run the browser under a debugger?