Chrome Loading Problem on Mac After Update? Here’s the Real Cause and Fix

Quick answer: If mac Chrome tabs keep reloading after update, start with checking Memory Saver, disabling extensions, and testing a fresh Chrome profile. This is usually caused by tab discarding, an extension conflict, a damaged browser profile, or an incomplete Chrome update. Do not reset, reinstall, or wipe anything until these safer checks are complete.

If the problem started right after updating Chrome on your Mac, the fastest fix is usually to turn off Memory Saver, test the same tabs with all extensions disabled, and compare behavior in a new Chrome profile before making bigger changes.

Quick Fix Checklist

• Turn off Memory Saver in Chrome Settings > Performance.
• Open chrome://discards and see whether Chrome is discarding the affected tabs.
• Disable all extensions in chrome://extensions, then test the same tabs again.
• Try the same pages in a new Chrome profile.
• Open Chrome About and let it finish checking for updates.
• Fully quit and reopen Chrome, not just the window.
• Check whether the issue affects all tabs or only certain websites.
• Test the same sites in another browser to separate Chrome from site behavior.

Causes

When Mac Chrome tabs keep reloading after update, the problem is usually inside Chrome itself, not macOS. Updates can change performance behavior, expose a bad extension, or break an existing profile that was already unstable.

Cause	What happens	Best fix
Memory Saver or tab discarding	Inactive tabs unload and refresh when you switch back.	Turn off Memory Saver and check chrome://discards.
Extension conflict	An extension forces refreshes, breaks sessions, or interferes with tab state.	Disable all extensions and re-enable one at a time.
Corrupted Chrome profile	Only one profile keeps reloading tabs or losing session state.	Test a new profile and compare behavior.
Incomplete or buggy update	Chrome behaves differently right after updating or restarting.	Finish the update check, relaunch Chrome, and retest.
Site-specific session behavior	Only certain websites reload, especially dashboards or web apps.	Test another browser, another profile, or another account.
Cached browser state conflict	Old site data or service worker state clashes with the new Chrome version.	Clear site data for the affected site only, not all browsing data.

Step-by-Step Fix

1. Turn off Memory Saver first.
   Open Chrome, go to Settings > Performance, and disable Memory Saver. After some updates, this setting becomes more aggressive and can make tabs reload whenever you return to them.
2. Check whether Chrome is discarding tabs.
   Type chrome://discards in the address bar. Look at the tabs that keep reloading and see whether they are marked as discarded. If they are, Chrome is unloading them to save resources rather than the website crashing on its own.
3. Disable every extension.
   Go to chrome://extensions and switch them all off. Then reopen the same tabs. If the reloads stop, re-enable extensions one by one until the problem returns. Tab managers, ad blockers, session tools, and productivity extensions are common triggers after updates.
4. Test a fresh Chrome profile.
   Create a new Chrome profile and open the same websites there. If the new profile works normally, your main profile likely has damaged settings, extension data, or session storage.
5. Confirm Chrome finished updating cleanly.
   Open Chrome > About Google Chrome and let it check again. If Chrome says a relaunch is needed, do that. A partially applied update can leave tab behavior unstable until the browser fully restarts.
6. Fully quit Chrome.
   Use Chrome > Quit Google Chrome, then reopen it. This clears temporary browser session state without deleting your data. Do not jump to reinstalling yet.
7. Check whether only specific sites reload.
   If only Gmail, dashboards, banking sites, or web apps reload, the issue may be tied to site cookies, service workers, or account sessions rather than all tabs. Test a few simple sites like a news page or search results to compare.
8. Clear site data for one affected website.
   This is the safest advanced fix before a reset. Open the affected site, click the lock or site controls icon in the address bar, and clear site data for that site only. Then sign in again and retest. This can fix update-related conflicts with cached app data or service workers without wiping all Chrome data.
9. Try Incognito mode.
   Open the same site in an Incognito window. If the tab stays stable there, the issue is usually tied to extensions, cookies, cached site data, or your normal profile state.
10. Check whether hardware acceleration changed after the update.
    Go to Settings > System and test Chrome with hardware acceleration toggled the opposite way from its current setting, then relaunch. This is less common, but some Chrome updates trigger tab redraw or reload-like behavior on certain pages.

Still Not Working

If Chrome tabs still keep reloading after the steps above, narrow the issue before you reset or reinstall anything.

• Only on Wi-Fi, not mobile hotspot: the network may be interrupting sessions or forcing captive portal checks. Test the same tabs on another network.
• Only on one browser profile: your profile is the problem, not Chrome globally. Keep using the working profile and migrate bookmarks and passwords later.
• Only in Chrome, not Safari or Firefox: this points to a Chrome-specific update conflict, extension issue, or profile corruption.
• Only one account is affected: sign out of that site and back in, or clear site data for that domain only. Account-level session loops can look like tab reloads.
• Only after the recent update: check Chrome Help or release notes for known regressions affecting Memory Saver, extensions, or tab lifecycle behavior.
• All networks and all websites: focus on Chrome settings, extensions, and profile state rather than the websites themselves.
• Only certain websites reload in every browser: the site may be forcing refreshes, timing out sessions, or having a service issue.
• Another device on the same account works fine: the issue is local to this Mac’s Chrome profile or browser data, not your Google account.

If none of those branches isolate the cause, use Chrome’s built-in cleanup path in this order: test a new profile, remove the one bad extension if found, clear site data for affected domains, then consider a Chrome settings reset. Only consider reinstalling Chrome after you confirm the problem also happens in a fresh profile, because reinstalling often does not fix profile-based tab reload problems.

Before any reset or reinstall, export bookmarks and make sure sync is complete. That prevents unnecessary data loss when the real cause is just one extension, one profile, or one site’s cached state.

Why do my Chrome tabs keep reloading after an update on Mac?
The most common causes are Memory Saver, tab discarding, an extension conflict, corrupted profile data, or a Chrome update that did not apply cleanly.

How do I stop Chrome from reloading tabs on my Mac without reinstalling?
Turn off Memory Saver, disable all extensions, check chrome://discards, and test the same tabs in a new Chrome profile before trying anything more drastic.

Why do only some Chrome tabs reload after the update?
That usually means the issue is site-specific or tied to one extension, one account session, or cached data for that website rather than all of Chrome.

Can a Chrome update change tab behavior on Mac?
Yes. Updates can change performance settings, tab lifecycle behavior, extension compatibility, and how Chrome handles cached site state.

Should I reset or reinstall Chrome right away?
No. First rule out Memory Saver, extensions, profile corruption, and site data conflicts. Those are safer checks and are more likely to fix the problem.

Frequently Asked Questions