FIX Chrome Out of Memory Errors: 5 Fixes Ranked (2026)

Key takeaways

• Figma, Miro, and dashboards routinely use 500 MB to 2 GB per tab. Chrome crashes without warning once a renderer hits the ceiling.
• V8 heap doesn’t shrink gracefully under pressure. The OS terminates the renderer process, losing all unsaved work.
• Make room before it crashes: discard idle tabs at chrome://discards/, and reload Figma proactively if it approaches 3.5 GB.

You’re mid-session in Figma or a data dashboard, and suddenly: “Aw, Snap!” with an Out of Memory message. The renderer process for that tab exhausted available RAM — or hit V8’s per-process memory ceiling. Modern single-page apps can use 500 MB to 2 GB per tab. When system RAM is saturated across multiple processes, Chrome terminates the renderer rather than allow an OS-level crash.

Quick Diagnosis

Fix 1: Identify the Crashing Tab’s Memory Usage

Before a crash, the tab’s memory footprint is visible in Chrome Task Manager.

1. Press Shift + Esc to open Chrome Task Manager.
2. Click Memory Footprint to sort by highest usage.
3. Watch the top entry. If it is growing continuously without stabilizing, that tab is the source.
4. For Figma, Miro, or similar WebGL apps: if memory approaches 3.5-4 GB in one tab, save your work immediately and reload the tab to reset the heap.
5. Note the tab name before the crash for future identification.

Fix 2: Force Discard Inactive Tabs

Chrome’s built-in discard page lets you manually free memory from specific tabs without closing them.

1. Go to chrome://discards/ in the address bar.
2. The table shows every open tab with its memory state (Active, Loaded, Discarded).
3. Click Urgent Discard on any tab you are not currently using.
4. The tab stays visible in the tab bar with a loading indicator — it reloads when you click it.
5. After discarding 5-10 inactive tabs, check Chrome Task Manager to confirm total memory has dropped.

Fix 3: Close Electron Apps to Free Shared RAM

Electron apps — Discord, Slack, Spotify, VS Code — are each their own Chromium browser instance. They compete for the same system RAM as Chrome.

1. Check Windows Task Manager (Ctrl+Shift+Esc) or macOS Activity Monitor for Electron-based apps consuming RAM.
2. Quit Discord, Slack, or Spotify when not actively using them — each can consume 200-500 MB.
3. On Windows, right-click the taskbar icon and select Quit (not just close the window, which often leaves Electron running in the background).
4. Check that the app is fully gone from Task Manager before opening a new Chrome tab.

Fix 4: Increase Windows Virtual Memory

On Windows, the Commit Limit is the sum of physical RAM and pagefile. When Chrome’s total Commit Charge exceeds this limit, new tab loads fail.

1. Open System Properties — press Win + R, type sysdm.cpl, press Enter.
2. Click the Advanced tab, then Settings under Performance.
3. Click the Advanced tab, then Change under Virtual Memory.
4. Uncheck Automatically manage paging file size for all drives.
5. Select your system drive (C:), choose System managed size, and click Set.
6. Click OK through all dialogs and restart Windows.

System-managed virtual memory lets Windows expand the pagefile as needed, raising the Commit Limit ceiling.

Fix 5: Restart the GPU Process

Chrome’s GPU Process handles hardware-accelerated rendering for all tabs. A growing GPU Process can consume 1 GB or more and contribute to system-wide RAM pressure.

1. Open Chrome Task Manager (Shift + Esc).
2. Find the GPU Process row.
3. Click End Process — Chrome restarts it automatically within seconds.
4. Check total memory before and after. A successful reset often reclaims 300-700 MB.

Preventing OOM Before Chrome Triggers It

If you work with memory-intensive apps like Figma or data dashboards and keep many tabs open alongside them, automatic tab suspension helps prevent crashes before they happen. SuperchargePerformance discards background tabs via chrome.tabs.discard() before RAM pressure reaches the crash threshold. You can whitelist figma.com or miro.com so those tabs are never suspended while everything else is discarded aggressively.

If you only have a few tabs open when crashes occur, the extension won’t help much — the problem is the individual tab’s memory usage, not competition from other tabs.

Technical Background

Chrome’s multi-process architecture assigns each tab, extension, and service worker its own isolated OS process. This improves security and crash isolation — a failed tab cannot corrupt another — but multiplies memory overhead because each process duplicates shared browser engine state.

The V8 JavaScript engine allocates a separate heap per renderer process. On 64-bit systems, the theoretical per-process limit is high, but practical limits appear much earlier as RAM fills across all processes. When a renderer’s allocation request is rejected by the OS, V8 throws an Out of Memory exception and Chrome shows the “Aw, Snap!” page.

The most effective prevention is keeping total RAM commit low by discarding inactive tabs before any single tab hits the ceiling.

For related issues, see Fix Chrome Not Enough Memory Error, Fix Figma Out of Memory in Chrome, and Fix STATUS_BREAKPOINT Crashes.