"Aw, Snap! Something went wrong while displaying this webpage" is Chrome's crash page for a single tab. The renderer process that runs the page terminated unexpectedly, so Chrome replaced the content with a sad-face icon and an error code. The rest of the browser keeps working, which is the point of its multi-process design. Edge shows a similar "Aw, Snap!" screen because it shares the engine.
This is different from network errors. The page may have loaded fine, and then the process running it died. Typical reasons are running out of memory, a browser or driver bug, an extension, or a page that overwhelms the machine.
Read the error code
The text under the icon helps narrow the cause:
- Out of Memory (
Error code: Out of Memory): the tab or the machine ran out of RAM.STATUS_BREAKPOINTon Windows is a generic crash code that Chrome also uses when it deliberately aborts, including on allocation failure, so treat it as a hint rather than proof. - STATUS_ACCESS_VIOLATION (Windows) or SIGSEGV (Linux, macOS): the renderer accessed invalid memory. This is a browser, GPU driver, extension or antivirus compatibility bug, not a fault in your site's HTML.
- STATUS_INVALID_IMAGE_HASH: Windows code integrity rejected a module, often a DLL injected by security software or a damaged installation.
- RESULT_CODE_HUNG: the renderer stopped responding and was killed.
- SIGILL, SIGTRAP: low-level faults, again usually environment or version related.
You can also open chrome://crashes to see recorded crashes, though reporting may be disabled by default, and chrome://version to check your browser build.
If you are a visitor
- Reload the tab. One-off crashes happen and clear on retry.
- Close other tabs and apps. Memory pressure is the most common cause. Check Chrome's Task Manager (Shift+Esc) to see which tab is using the most.
- Test in an Incognito window. Extensions are disabled there by default. If it works, disable extensions one by one in
chrome://extensions. - Update Chrome. In
chrome://settings/help. Crash bugs are fixed regularly. - Turn off hardware acceleration in Settings, System, then relaunch. Graphics driver bugs are a known source of renderer crashes. Update your GPU driver too.
- Scan for conflicting software. Some antivirus tools, injection-based overlays, and screen recorders crash Chrome. Temporarily disabling them is a quick test.
- Reset or create a new profile. A corrupt profile can cause repeated crashes on one machine only.
- Free disk space and check RAM. A nearly full disk makes the swap file unusable and crashes follow.
- Reboot. It clears leaked GPU and memory state.
If you own the site
If many visitors report the same page crashing, the page itself is demanding too much. Reproduce it in a clean profile on a mid-range device, and look at the following.
Memory use
Open DevTools, Memory panel, and take a heap snapshot after interacting with the page. Look for steadily growing arrays, detached DOM nodes, and event listeners that are never removed. Infinite scroll lists that keep every item in the DOM, giant in-memory JSON, and huge canvases are common culprits. See memory leak.
Page weight and DOM size
Pages with very large DOMs, hundreds of megabytes of images decoded at once, or giant tables use heavy memory. The पेज वेट एनालाइज़र shows what the page transfers, and the वेबसाइट हेल्थ चेक flags obvious problems. Use responsive images and lazy loading; see image optimization with WebP and AVIF.
Runaway JavaScript
Infinite loops, endless recursion, and giant synchronous work can hang the renderer, resulting in RESULT_CODE_HUNG. Use the Performance panel to find long tasks and move heavy work to a Web Worker.
Third-party scripts
Ad, widget and chat scripts can crash tabs, especially on low-end phones. Disable them one at a time to find the culprit, using the थर्ड-पार्टी स्क्रिप्ट चेकर to list what loads.
WebGL, video and large canvases
Unbounded canvas sizes and WebGL contexts that are never released can exhaust GPU memory. Cap canvas dimensions and dispose of resources you no longer need.
Check real-user impact
Slow or heavy pages also hurt Core Web Vitals. If crashes cluster on certain devices, check for spikes in your analytics by browser and device memory. An अपटाइम मॉनिटर will not notice a client-side crash, because the server responds normally, so use browser error reporting for that.
When to report it
If the crash reproduces in a clean profile with no extensions on current Chrome, file a report at the Chromium bug tracker with the URL, your OS, and the crash ID from chrome://crashes. Check the tracker for existing reports first.
अगले कदम
- Cut page weight with website slow diagnosis.
- Review Core Web Vitals.
- Compare with a network failure such as ERR_CONNECTION_RESET.
- Check that the server itself responds using the HTTP Header Checker.
सामान्य प्रश्न
Is Aw, Snap a virus?
No. It is Chrome reporting that a tab crashed. Persistent crashes on many sites can come from malware or conflicting software, so scanning is reasonable.
Why does it happen on only one site?
That page may use more memory or trigger a bug through its scripts, video, or graphics. Test with extensions off and report it to the site owner.
Will reinstalling Chrome help?
Sometimes, if files are corrupt or a bad update was applied. Try a clean profile and a driver update first.
Does Edge have the same error?
Yes, Edge uses the same engine and shows a similar message. The same fixes apply.
Get notified when this fix updates
Plus occasional practical tips on uptime and monitoring, nothing else. Unsubscribe anytime.
यह पेज सामान्य जानकारी है, जिसे हमारी संपादकीय टीम ने लिखा है और दस्तावेज़ीकरण बदलने पर अपडेट किया जाता है। सर्वर और प्रदाता अलग-अलग होते हैं, इसलिए बदलाव पहले सुरक्षित तरीके से जाँचें। देखें: संपादकीय नीति और अस्वीकरण.