FIX Chrome Memory Leaks on Windows 11: 5 Solutions (2026)

Key takeaways

• Close a dozen tabs and Chrome still shows 6 GB an hour later. That’s a leak (the memory was never released).
• Three culprits: zombie renderer processes, extension background pages, and the GPU Process holding VRAM after video tabs close.
• Shift+Esc → sort by Memory → watch what keeps climbing. End Process on the GPU row reclaims 500 MB+ in seconds.

You closed a dozen tabs an hour ago and Chrome is still using 6 GB of RAM. Welcome to the memory leak. Unlike normal high usage, a leak means memory grows continuously — processes that should have released RAM after you closed a tab are holding onto it indefinitely.

The leaked memory accumulates in Windows’ Commit Charge and causes system-wide slowdowns even when Chrome is not the foreground app. Extensions, lingering JavaScript event listeners, and zombie renderer processes are the most common culprits.

Quick Diagnosis

Use this table to identify which type of memory problem you have before applying fixes:

Fix 1: Identify the Leaking Process

Press Shift + Esc to open Chrome Task Manager. This shows every process Chrome is running — tabs, extensions, subframes, and service workers — with individual memory figures.

1. Click the Memory Footprint column header to sort by highest usage.
2. Look for processes labeled Subframe — these are often ad iframes running in background tabs.
3. Look for Extension entries using more than 100 MB consistently.
4. Watch the list over 5-10 minutes. A leaking process grows without pause even when the tab is idle.
5. Click End Process on any suspect entry to confirm it is the source — if overall memory drops significantly, that process was the leak.

Fix 2: Remove or Disable Leaky Extensions

Extensions are the most common source of Chrome memory leaks on Windows 11 because they run in persistent background pages.

1. Go to chrome://extensions/ in the address bar.
2. Click Details on any extension using high memory in Chrome Task Manager.
3. Toggle off extensions one at a time, then check Task Manager memory after 2-3 minutes each.
4. If memory stops growing after disabling a specific extension, that extension is the leak source.
5. Check for updates: click Update at the top of chrome://extensions/ — many leak bugs are fixed in newer versions.

Fix 3: Restart the GPU Process

Chrome’s GPU Process handles hardware acceleration for all tabs. It can grow to 1 GB or more on Windows 11 when multiple video tabs have been open and closed.

1. Open Chrome Task Manager with Shift + Esc.
2. Find the row labeled GPU Process.
3. Click End Process — Chrome restarts the GPU process automatically within seconds.
4. Check the memory figure after the restart. This often reclaims 500 MB or more without closing any tabs.

Fix 4: Disable Unused Preloading

Chrome’s page preloading caches pages in memory that you may never visit, which compounds memory leak accumulation.

1. Open Settings (three-dot menu > Settings).
2. Go to Performance in the left sidebar.
3. Under Speed, set Preload pages to No preloading or disable it entirely.
4. Restart Chrome once for the change to take effect.

Fix 5: Suspend Office 365 and Web Editor Tabs

Microsoft 365 web apps (Word Online, Excel, SharePoint) are a specific and common leak source. These apps allocate memory for document rendering, undo history, and real-time collaboration. When you close a Word Online tab, the DOM nodes tied to the document editor are not always released — especially after the tab has been open for hours. With 10 or more Office tabs open, Chrome can hold 200–500 MB of stale editor memory.

1. Navigate to chrome://discards/ in the address bar.
2. Find an inactive Office or document tab in the list.
3. Click Urgent Discard — Chrome immediately frees the memory for that tab’s renderer.
4. The tab stays visible in the tab bar and reloads when you click it.

Preventing Memory Buildup from Background Tabs

If you routinely keep 20+ tabs open and find yourself running these fixes every week, a tab suspender addresses the root problem. SuperchargePerformance automatically discards inactive tabs via Chrome’s chrome.tabs.discard() API — forcing the renderer to release memory rather than waiting for garbage collection (chrome.tabs.discard() API). It also blocks ad iframes at the network level, preventing Subframe processes from launching in the first place.

Pinned, audible, and form-in-progress tabs are never suspended. Not everyone needs an extension for this — if you typically keep under 15 tabs and the leak is coming from one bad extension, fixing that extension is the right call.

Technical Background

Chrome uses a multi-process architecture: each tab and extension runs in a separate OS process for security and crash isolation. When a tab is closed, the renderer process should terminate and return its memory to Windows. However, JavaScript event listeners that hold references to DOM nodes, or extensions that communicate with tab content, can keep these processes alive in a “zombie” state.

Windows 11 memory compression can mask this initially. The OS compresses idle RAM pages, making the Commit Charge appear lower than the actual allocated memory. Once compressed RAM fills the physical limit, Windows starts writing to the pagefile (SSD swap). This thrashing degrades performance and causes audible drive activity on systems without SSDs.

The most reliable long-term fix combines two approaches: identifying and removing the leaking extension or site, and using tab suspension to prevent memory from accumulating before the leak can compound.

For related issues, see Fix Chrome High Memory Usage and Fix Chrome Out of Memory Errors.