Chrome Memory Leak? How to Tell, Find the Tab and Fix It

A Chrome memory leak shows up as a slow climb. In the morning Chrome uses a reasonable amount of memory. By late afternoon it uses twice as much, with the same tabs open, and the fan has been running for an hour. Restart Chrome and the number drops back down.

The good news: the leak is almost never Chrome itself. It is usually one tab or one extension, and Chrome gives you the tools to find it in a few minutes. This guide shows how to tell a real leak from normal growth, how to catch the process responsible, and what to do about it.

The short answer#

• A leak is one process growing for hours while you do nothing new in it.
• Find it in Chrome's task manager by sorting by Memory footprint and checking again later.
• Reload or close a leaking tab; update or remove a leaking extension.
• Stop it coming back by letting idle tabs sleep and restarting Chrome now and then.

What we measured on a Mac#

Tested on a MacBook Pro (M1 Pro) with 16 GB of RAM, macOS 26.3, Chrome 155, October 21, 2026. We opened a simple page and ran a script that kept adding data it never released, the way a leaking web app does. Memory is the total footprint of every Chrome process in a fresh test profile, read with macOS's footprint tool.

Two lessons. A leak looks like a line that climbs steadily while you do nothing. And a reload does not always give the memory back right away, because the tab can keep the same process; closing the tab (and opening the page again in a new one) does.

Leak or normal growth?#

Chrome's memory goes up for good reasons all day. A page you scroll loads more images. A new tab starts a new process. Web apps keep data you looked at so they can show it again quickly. None of that is a leak.

A leak has a signature:

If you see the right-hand column, keep reading.

How to find the leaking tab or extension#

Chrome runs each site and many extensions in their own processes, so its task manager can show you exactly which one is growing.

1. Open Chrome's task manager. On Windows press Shift+Esc. On a Mac, open the Window menu and choose Task Manager. On any system, use the three-dot menu, then More tools, then Task manager.
2. Click the Memory footprint column so the largest rows are at the top.
3. Write down the top five rows and their numbers.
4. Keep working normally for an hour, then check again.
5. The row that grew a lot while you did nothing new in it is your suspect.

Rows starting with Tab: are web pages. Rows starting with Extension: are extensions. GPU Process and Browser are Chrome's own processes. If you are new to this window, our guide to Chrome using too much memory explains how to read it.

If a tab is leaking#

Long-running web apps are the usual suspects: chat, email, dashboards that refresh every few seconds, social feeds with infinite scroll, and pages that play ads.

• Reload it. A reload throws away everything the page built up. If memory returns to normal and climbs again over the next hours, the site leaks.
• Close it when you are not using it. Or let Chrome put it to sleep: Memory Saver discards idle tabs, which frees leaked memory along with everything else.
• Use the site's desktop app if it has one, or open it in its own window so you can close it at the end of the day.
• Report it to the site. Leaks are bugs, and developers can find them with Chrome DevTools' memory tools.

If an extension is leaking#

1. Open chrome://extensions.
2. Check for updates by turning on Developer mode at the top right and clicking Update, then turn Developer mode off again.
3. If the extension still grows, switch it off for a day.
4. If the problem disappears, remove it or look for an alternative.

Extensions that run on every page cost memory in every tab, even when they do not leak. Our guide to Chrome extensions slowing down your computer shows how to find the costly ones.

If Chrome's own processes grow#

Sometimes the GPU Process or the Browser row is the one that climbs.

• Update Chrome from the three-dot menu, then Help, then About Google Chrome. Leak fixes ship in regular releases.
• Restart Chrome fully. On a Mac use Quit Google Chrome from the Chrome menu, not just closing the window.
• Check graphics. A GPU process that keeps growing can be a graphics driver problem. Update your graphics driver on Windows, or test with hardware acceleration off (Settings, then System, then Use graphics acceleration when available). If Chrome then freezes instead, see Chrome freezing.

For web developers: confirm the leak#

If the leaking page is yours, Chrome DevTools can prove it. The Memory panel takes heap snapshots you can compare, and the Performance panel records memory over time. Google's DevTools guide on fixing memory problems walks through detached DOM nodes, growing arrays and other common causes. Take a snapshot, use the page, take another, and compare what was allocated and never freed.

Keep leaks from piling up#

You cannot fix every website. You can limit how long a leak runs.

• Let idle tabs sleep. A discarded tab gives back all its memory, leaked or not. Turn on Memory Saver under Settings, then Performance.
• Restart Chrome once in a while. If you leave it running for a week, a weekly restart resets every process. Chrome reopens your tabs if you set On startup to Continue where you left off.
• Keep fewer tabs alive. The fewer pages running, the fewer chances to leak.

If you want a fixed rule rather than Chrome's judgment, Cleaner Pro sleeps any tab after 30 minutes without use and skips the tab you are on, pinned tabs and protected sites. Its free Tab Manager side panel sorts tabs by estimated memory, which makes a growing tab easy to spot. Pro is a one-time $19.99 for up to three browsers.

What does not fix a leak#

• Clearing cache and cookies. The cache lives on disk. It has nothing to do with memory a page is holding right now.
• "RAM cleaner" apps. They force memory out and Chrome loads it right back.
• Reinstalling Chrome. Your extensions and tabs come back with sync, leak included.

The bottom line#

A Chrome memory leak is one process that keeps growing while it should be idle. Find it in the task manager, reload or close the tab, update or remove the extension, and let Memory Saver or an extension sleep idle tabs so leaks never run for days. For everything else that makes Chrome heavy, see our guide to Chrome using too much memory.