The Endless Crash Loop
Google Chrome isolates every single tab into its own distinct background process. If a specific website contains faulty JavaScript, a massive memory leak, or gets caught in an infinite loop, that individual tab will freeze and become unresponsive, eventually displaying the infamous “Aw, Snap!” error page. By default, Chrome attempts to be helpful by automatically trying to reload the unresponsive tab after a short period. However, if the underlying website code is fundamentally broken, Chrome will repeatedly reload the tab, crash it again, and reload it again, creating a frustrating infinite loop that drains your CPU resources and battery life.
Breaking the Reload Cycle
To regain control over your browser’s resources and stop Google Chrome from automatically attempting to reload unresponsive or crashed tabs, you must modify the browser’s hidden experimental flags.
Open a new tab in your Google Chrome browser. Click into the address bar, type exactly chrome://flags, and press Enter to open the internal experiments page. In the search box at the top of the page, type Automatic tab discarding or Reload. Look specifically for a flag named Enable Auto-Reload of Crashed Tabs or Offline Auto-Reload Mode. Click the dropdown menu next to this specific flag (which will likely be set to “Default”) and change the setting to Disabled. A blue Relaunch button will appear in the bottom right corner. Click it to restart the browser. Moving forward, if a tab crashes, it will stay dead on the “Aw, Snap!” page until you explicitly click the reload button yourself, preventing the infinite crash loop.