Chrome Memory Saver Not Working? Why You See No Change

Chrome Memory Saver works, but it is reactive: it discards inactive tabs only when your system reports memory pressure or its on-device model predicts you won’t return to a tab. On a roomy machine, that threshold may never trip, so no tab is ever discarded and you feel nothing. As of June 2026 (Chrome 149), “Memory Saver not working” is almost always Memory Saver waiting, not Memory Saver broken.

Check Whether It Discarded Anything (2 Minutes)

Before assuming the feature is dead, confirm what it has actually done. Type chrome://discards into the address bar and press Enter. You get a table of every open tab with two columns that settle the question:

• Discarded — reads Yes if Chrome has freed that tab’s memory, No if the tab is still fully resident.
• Last Active — how long the tab has sat untouched.

If you have a dozen tabs you abandoned hours ago and every Discarded cell reads No, Memory Saver has not acted on a single one. That is the most common “it’s not working” case, and the table just proved the feature is idle rather than broken.

To prove it can free RAM, find a heavy idle tab in that table, open Chrome’s own Task Manager (Shift+Esc on Windows and Linux, or the Window menu on macOS), note the tab’s memory figure, then click Urgent Discard on its chrome://discards row. The tab drops out of Task Manager’s renderer list and its footprint collapses to a few kilobytes. The mechanism is fine. The trigger is the issue.

Why You See No Change

Memory Saver only fires under two conditions: the operating system signals real memory pressure, or the on-device revisit model (added in Chrome 140, September 2025) flags a tab as unlikely to be reopened. Neither condition cares about a clock.

On a 16 GB laptop with 15 mixed tabs, Chrome might sit at 4 GB all afternoon and never cross the pressure line. Your idle tabs stay fully loaded the entire time. Nothing is wrong, and nothing is freed, because the feature is built to step in during a shortage, not to keep your footprint trim by default.

The mismatch between the first column and the second is the whole story behind the “no difference” complaint. The feature is quietly correct; it just optimizes for a moment you may not reach.

The Protections That Keep Heavy Tabs Resident

Even when Memory Saver does fire, it deliberately skips the tabs most likely to be eating your RAM right now:

• The active tab you’re looking at
• Pinned tabs
• Tabs playing audio (a music or video tab)
• Tabs with unsubmitted form input
• Anything on your Always keep active exclude list

These are the right calls. Discarding a half-written email or a live video call would be worse than the RAM it saves. But they also mean the Figma board, the Meet call, and the YouTube tab, often the three heaviest things open, frequently stay resident. So even an actively-working Memory Saver can leave your total RAM looking barely changed, which reads to most people as “it did nothing.”

When the Reactive Model Is Already Enough

Stay on the built-in feature with no extra tooling if you keep fewer than 10 tabs, run on a machine where memory pressure actually arrives (8 GB or less is common), and don’t care about seeing the numbers. In that setup Memory Saver trips often, frees real RAM, and asks nothing of you. It is a good default and it is doing its job.

The gap opens on a roomy machine with a heavy tab habit: 20-plus tabs on 16 GB, where pressure trips late or never, so you spend the session with idle tabs fully loaded. There, “reactive” means “mostly idle,” and the RAM you could reclaim sits unrealized for hours.

Closing the Gap With Proactive Suspension

A timer-based suspender attacks the timing problem directly. Instead of waiting for pressure, SuperchargePerformance discards a tab once it has been inactive for a fixed window (5 or 15 minutes on the free tier, a custom value on PRO) through the same chrome.tabs.discard() call Chrome uses internally. The RAM comes back before your machine slows down, freeing most of each parked tab’s memory, not after a shortage forces it.

The honest framing: the extension is not faster magic, it runs the same discard the browser does. Its edge is when (a clock you set, not a pressure spike) and visibility (a per-tab RAM figure so you can confirm the saving instead of squinting at chrome://discards). It also blocks ads on the active tabs Memory Saver leaves loading at full weight, and it runs entirely on your own machine with no account and nothing phoned home.

If you want the full feature-by-feature breakdown of the built-in tool first, our Chrome Memory Saver tested review rates it across setup, timing, and visibility. To see exactly how the timing gap plays out at 30 tabs, the tab suspender vs Memory Saver data measures both side by side.

Settle It On Your Own Machine

If chrome://discards shows everything as No and your tabs sit idle for hours: Memory Saver is waiting for pressure that isn’t coming, so reach for a timer. If pressure does arrive on your hardware and tabs get discarded on their own: the built-in feature is already doing the work, and you don’t need anything more.