Why does Chrome use so much RAM?

Chrome assigns each tab and extension its own process for security and isolation. The trade-off is memory overhead.

◇ Browser Errors

Chrome out of memory — How to fix on Windows

Chrome's 'out of memory' errors happen long before the system actually runs out of RAM — they trip when a single tab process hits the per-process limit, or when too many extensions inflate idle RAM.

Time: 10 min
Difficulty: easy
Applies to: Windows 11, Windows 10
Updated: May 25, 2026

Error message

Aw, Snap! Out of Memory

Symptoms

▸'Aw, Snap! Out of memory' on heavy pages (Slack, Notion, Google Docs)
▸Tabs spontaneously reload with the same error
▸Task Manager shows Chrome using 4+ GB of RAM at idle

Likely causes

▸Too many tabs sharing the same process
▸Memory-hungry extensions (ad-block lists, password managers, screen readers)
▸Site with an infinite loop or memory leak (often legacy SPAs)
▸Hardware acceleration leaking GPU memory

How to fix it — step by step

01
Open Chrome's Task Manager
Shift+Esc inside Chrome. Identify which tab or extension is using the most memory.
02
Disable the worst extensions
Same as the STATUS_ACCESS_VIOLATION fix — disable all, re-enable one at a time.
03
Enable Memory Saver
chrome://settings/performance → toggle Memory Saver on. Inactive tabs free their memory automatically.
04
Force one process per site
Launch Chrome with --process-per-site as a test. If memory drops significantly, the per-tab process model was the issue.