Browser Tab Crashing — Memory Leak and 'Aw Snap' Out of Memory Error
About Browser Tab Crashing
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. This guide covers everything you need to know about this topic, including common causes, step-by-step solutions, and answers to frequently asked questions.
Here are the key things to understand: 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. Understanding these fundamentals will help you diagnose and resolve this issue more effectively.
The most common reasons this occurs include: 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. Identifying the root cause is the first step toward finding the right solution.
To resolve this, follow these recommended steps: Check memory usage: Chrome > Shift+Esc (Task Manager) to see per-tab memory. Disable extensions one by one to identify if an extension is the memory hog. For web developers: DevTools > Memory > take heap snapshots before and after interactions, compare retained objects. Enable Chrome's memory saver: Settings > Performance > Memory Saver (suspends inactive tabs). If a specific site crashes: close other tabs to free memory, reduce the number of open tabs. If these steps do not resolve the issue, consider consulting additional resources or a qualified professional.
This article is part of our Browser Errors collection on Error Codes Wiki. We provide comprehensive, up-to-date information to help you find solutions quickly.
Quick Answer
How much memory can a single tab use?
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.
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
- 1Check memory usage: Chrome > Shift+Esc (Task Manager) to see per-tab memory
- 2Disable extensions one by one to identify if an extension is the memory hog
- 3For web developers: DevTools > Memory > take heap snapshots before and after interactions, compare retained objects
- 4Enable Chrome's memory saver: Settings > Performance > Memory Saver (suspends inactive tabs)
- 5If a specific site crashes: close other tabs to free memory, reduce the number of open tabs