Chrome: Aw, Snap! Something went wrong while displaying this webpage. Error code: STATUS_ACCESS_VIOLATION / SIGILL / Out of Memory
A Chrome tab crashed — out of memory, a faulty extension, a graphics/driver issue or a very heavy page.
Aw, Snap! Something went wrong while displaying this webpageError code: Out of Memory Meaning
The "Error code" under the sad tab is the clue: "Out of Memory" (RAM exhausted), STATUS_ACCESS_VIOLATION / STATUS_BREAKPOINT / SIGILL (crash in the renderer or a driver/extension), RESULT_CODE_HUNG (page froze), or STATUS_INVALID_IMAGE_HASH (third-party software injecting into Chrome).
Common causes
- Too many tabs or a memory-hungry site
- Extension crashing the renderer
- GPU driver or hardware acceleration problem
- Third-party software injecting DLLs (antivirus, overlays)
- Corrupted profile or outdated Chrome
⚡ Quick fix
- Reload the tab and close other tabs/apps
- Test in incognito (extensions off) and disable extensions one by one
- Turn off hardware acceleration and update Chrome and GPU drivers
Detailed fix by platform
Chrome
- Settings → System → turn off "Use graphics acceleration when available", relaunch
chrome://crasheslists recent crashes- Settings → Reset settings if the profile is damaged
Windows
- Update GPU drivers; run
sfc /scannow; check for software that injects into Chrome (STATUS_INVALID_IMAGE_HASH)
How to diagnose
- Code — Exact error code on the sad tab?
- Extensions — Fixed in incognito?
- Memory — RAM and tab count?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- $ is not defined Console: Uncaught ReferenceError: $ is not defined (jQuery not loaded or loaded after your code)
- captive portal Browser: This network requires you to sign in — captive portal (hotel, airport, café Wi-Fi) blocking HTTPS sites
- DevTools failed to load source map DevTools: Failed to load source map — Could not load content for https://…/app.js.map: HTTP error: status code 404
Most viewed in Browser
Other ways to find it
Where this error sits
Origin: On your device. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 15 Oct 2026