Chrome Tabs Keep Reloading Even with Memory Saver Off

You can keep a writing site active in Chrome without keeping every old reference tab loaded. Add the editor to the site exceptions in Performance settings, using the address where the document actually opens. This keeps Memory Saver available for the tabs you no longer need while you work.

The switch alone does not settle every case. One Windows 11 user reported reloads in both Chrome and Brave despite disabling Memory Saver and having unused RAM. If you are in that position, save your draft and compare the same task with a tab-management extension turned off. That extension can discard a page independently of Memory Saver.

A reload, a resumed timer, and an error need different checks

Start with the visible result. Does the page show its loading screen again? Does it stay in place but update old information? Or does Chrome display an error? Write down which happened before changing settings. A stale dashboard and a newly loaded editor can feel equally disruptive, but the browser may have taken different actions.

Chrome’s lifecycle documentation describes discarding and freezing as separate states. A tab’s title can remain visible after the document has been removed from memory. Memory Saver proactively discards unused tabs; Chrome has also used discarding under memory pressure. If other applications become slow at the same time, inspect the running tasks as well as the tab settings.

Energy Saver can freeze eligible CPU-intensive background tabs. Google’s explanation of freezing says that focusing a frozen tab resumes its queued work with its state retained. If background updates stall while Energy Saver is active, use its address-bar control to turn it off for the session and compare. That test targets the pause; it does not explain every full document reload.

Add the editor’s address, not just the service’s homepage

Open the page you need to keep available in desktop Chrome, then choose the three-dot menu → Settings → Performance. Beside Always keep these sites active, select Add, then choose the currently open site. Google’s performance guide describes this site exception. Chrome on Android and iOS does not have these Performance controls.

A service may send you from a sign-in host to an editor on a different host. Make the exception while the editor is open, and read back the resulting entry. Keeping the authentication page active is not the same as matching the document where you spend the next hour working.

For manual entries, a bare domain such as example.com includes its subdomains. A leading dot, as in .work.example.com, limits matching to that host rather than its subdomains. Adding a path can narrow the entry to an editing area. These are illustrative addresses, not settings for a particular service. Avoid a blanket https://* entry when you only need one application: it covers all HTTPS sites.

If one document stays available and another still reloads, compare their actual addresses with the saved rule. They may use different hosts or routes. Broaden only the part needed for the second document, then repeat the same task. You can also choose a less aggressive Memory Saver level for other tabs, but the three levels are not published as a fixed schedule of minutes.

A tab manager can act independently of the setting you changed

Check any extension that suspends tabs, restores sessions, or automatically refreshes pages. The Chrome Tabs API includes a method that lets an extension request that a tab be discarded. The native Memory Saver switch is therefore not a master switch for every tool that can affect a tab.

Choose the three-dot menu → Extensions → Manage Extensions and temporarily turn off a suspected tab-management extension. Save your work first, then repeat the transition that normally triggers the reload. If the problem disappears with that extension off and returns after you enable it, you have a more specific configuration to investigate. Disabling several tools at once makes the result harder to attribute.

If the whole machine is struggling, open More tools → Task Manager in Chrome. Google recommends sorting tasks by memory to find resource-heavy activity, including background pages. Read the entries before ending anything. End Process can lose unsaved work in the selected task; it is not a way to preserve the editor you are trying to protect. Close tasks you no longer need and compare again.

On a work or school browser, some controls may be locked or extensions installed by an administrator. Look for the managed-browser notice in the menu or open chrome://management. Google’s managed-browser guide explains that administrators can restrict features. Send them the affected working URL and your reproduction steps if the relevant setting is unavailable.

Check whether this document actually followed a discard

For a closer look, open chrome://discards in another tab and locate the affected page. Chrome’s developer documentation uses this internal screen to investigate and test tab lifecycle behaviour. Merely appearing in the list is normal. Inspect the state associated with the page rather than treating every listed tab as discarded. Do not press a discard action on an unsaved working page just to see what happens.

Immediately after the unexpected reload, open More tools → Developer tools on the affected page and choose Console. You can also open Console with Ctrl+Shift+J on Windows or Linux, or Command+Option+J on Mac. Select the page’s top-level context, type the following read-only expression, and press Enter:

document.wasDiscarded

According to Chrome’s discard-detection guidance, a true result identifies a document loaded after a discard. It does not name the extension or browser condition responsible. A false result is not proof that everything worked correctly; this load simply is not marked as restoration after discarding. Do not manually reload again before checking, because you would then be examining a different load.

If you saw “Aw, Snap!” or a connection error, keep the exact message. Chrome’s error guide separates connection failures from page crashes and recommends investigating the site when other pages work but that one repeatedly crashes. A site exception will not repair a broken connection or the page’s own failing code.

A pinned tab cannot reconstruct text the site never stored

Chrome lists partially completed forms, pinned tabs, and active media among activities that may prevent deactivation. That helps explain why some idle-looking tabs remain loaded. It is not a guarantee that every custom editor will retain every unsent change, nor does pinning write a draft to your account.

The site must store and restore the state that matters: text, selections, and perhaps your place in a long feed. Google’s guidance to site developers is to save state as it changes or when a page moves into the background. There may be no final event at discard time in which to save it. An unsaved-changes warning seen when deliberately closing a tab is not a guaranteed warning before a discard.

For a long reply, use the service’s draft function and check its saved indication before leaving. If the form has no draft storage, compose substantial text in an appropriate editor and then paste it into the form. Keep work material in an approved location. This gives you content to return to even if the browser cannot retain the live page.

Use the same page to compare one change

Pick one saved document and note its address, the exception entry, and whether Memory Saver is on. Switch to the same reference page or application you normally use, then return. Record separately whether the document reloaded, background updates resumed, and the draft survived. Repeat after changing one setting or disabling one suspected extension.

If the editor remains available while old reference tabs reload, the exception is serving the intended workflow. If it still fails, send the site owner or administrator the address, error message, discard result if checked, and what happened with the extension disabled. Those details let the next investigation start from the remaining behaviour instead of another instruction to switch Memory Saver off.