◆Error Codes Wiki

Browser Tab Crash — Chrome Aw Snap, Firefox Tab Crash, and Recovery

Errorgeneral

Overview

Fix browser tab crashes including Chrome's 'Aw, Snap!' page, Firefox tab crash reports, and diagnosing memory exhaustion, extension, and GPU causes.

Key Details

  • Tab crashes occur when the renderer process for that tab encounters a fatal error
  • Chrome shows 'Aw, Snap!' (chrome-error://chromewebdata/) when a tab process crashes
  • Firefox shows 'Gah. Your tab just crashed.' with a report option
  • Modern browsers isolate tabs in separate processes — a crash in one tab does not affect others
  • Common causes: out of memory, GPU acceleration error, or corrupted page content

Common Causes

  • Page consuming too much memory (large images, infinite scroll, memory leak in JavaScript)
  • GPU acceleration conflict causing the renderer to crash
  • Extension injecting code that crashes the renderer process
  • Corrupted browser profile data
  • Hardware issue: faulty RAM causing random process crashes

Steps

  1. 1Reload the page: the crash may be transient
  2. 2Check memory usage: Chrome > Shift+Esc for Task Manager to see per-tab memory usage
  3. 3Disable GPU acceleration: Settings > System > Use hardware acceleration > toggle off, restart browser
  4. 4Try in incognito/private mode (no extensions) to rule out extension cause
  5. 5Clear browser cache and site data for the crashing page
  6. 6If all tabs crash: create a new browser profile to rule out profile corruption

Tags

tab-crashaw-snaprenderermemorygpu

Related Items

chrome-aw-snap-crashbrowser-javascript-heap-out-of-memory

More in General

printer-offlinePrinter Offline Error
Warning
driver-unavailablePrinter Driver Is Unavailable
Warning
spooler-errorPrint Spooler Error
Warning
pcl-xl-errorPCL XL Error — Subsystem Kernel
Warning
printer-duplex-printing-errorsPrinter Duplex (Double-Sided) Printing Errors — Jams, Alignment & Blank Pages
Warning
printer-usb-connection-errorsUSB Printer Errors — Not Detected, Driver Issues, and Connection Troubleshooting
Warning

Frequently Asked Questions

The site likely has a JavaScript bug, excessive memory usage, or content that triggers a browser rendering bug. Try: clearing the site's cache, disabling extensions, or opening in a different browser.