◆Error Codes Wiki

Browser Tab Crashing — Memory Leak and 'Aw Snap' Out of Memory Error

Errorgeneral

Overview

Fix browser tabs crashing with 'Aw, Snap!' (Chrome), 'Gah. Your tab just crashed' (Firefox), or out-of-memory errors caused by memory leaks in web pages.

Key Details

  • Browser tabs are sandboxed processes with memory limits (typically 2-4GB per tab)
  • Memory leaks in JavaScript, DOM references, or WebAssembly can gradually exhaust tab memory
  • Chrome shows 'Aw, Snap!' (SIGKILL/OOM), Firefox shows 'Gah. Your tab just crashed'
  • Common in long-running SPAs (Single Page Applications) that accumulate memory over time
  • Browser DevTools Memory tab can identify memory leaks by comparing heap snapshots

Common Causes

  • JavaScript detached DOM nodes still referenced in memory preventing garbage collection
  • Event listeners not removed when components unmount in SPA frameworks
  • Large data arrays, media buffers, or WebSocket data accumulating without cleanup
  • Browser extensions consuming excessive memory in the tab's process

Steps

  1. 1Check memory usage: Chrome > Shift+Esc (Task Manager) to see per-tab memory
  2. 2Disable extensions one by one to identify if an extension is the memory hog
  3. 3For web developers: DevTools > Memory > take heap snapshots before and after interactions, compare retained objects
  4. 4Enable Chrome's memory saver: Settings > Performance > Memory Saver (suspends inactive tabs)
  5. 5If a specific site crashes: close other tabs to free memory, reduce the number of open tabs

Tags

memory-leakcrashaw-snapoomtab

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

In 64-bit browsers: typically 2-4GB per tab (OS-dependent). In 32-bit browsers: about 1-1.5GB. Complex web apps (Google Maps, Figma, spreadsheets) can legitimately use 500MB-1GB. Memory leaks push usage beyond normal limits.