Guide

Chrome Keeps Killing ChatGPT in Background Tabs — Here's How to Stop It (2026)

Name: SuperchargeBrowser
Author: SuperchargeBrowser

Mar 3, 2026

If you switch tabs while ChatGPT (or Claude/DeepSeek) is generating code, you often return to a red "Network Error". This happens because Chrome aggressively throttles JavaScript timers in background tabs to save battery. When the tab is throttled, the WebSocket "heartbeat" fails, the server assumes you disconnected, and the generation terminates mid-sentence.

The Manual Fix

Drag to New Window: Pull the ChatGPT tab out into its own dedicated window and keep it visible on a second monitor.

Play Silent Audio: Run a 10-hour silence video in the background of the tab to trick Chrome into thinking it's media (messy workaround).

Disable Throttling Flag: Go to chrome://flags and search for "Throttle expensive background timers" (Note: Google frequently removes/renames this flag).

Drag to New Window: Pull the ChatGPT tab out into its own dedicated window and keep it visible on a second monitor.

Play Silent Audio: Run a 10-hour silence video in the background of the tab to trick Chrome into thinking it's media (messy workaround).

Disable Throttling Flag: Go to chrome://flags and search for "Throttle expensive background timers" (Note: Google frequently removes/renames this flag).

The Automated Fix

SuperchargePerformance offers a Smart Whitelist solution. The strategy is not to disable efficiency, but to direct it. You add chatgpt.com to the Supercharge Whitelist. Our engine then aggressively suspends everything else to free up resources, while explicitly acquiring a "Keep-Alive" lock for your AI tab to ensure the WebSocket connection remains pristine.

Technical Root Cause Analysis

Real-time AI streaming relies on WebSockets or Server-Sent Events (SSE).

The Throttling: To save battery, Chrome aligns background JavaScript timers to wake up only once per minute.

The Failure: If the AI server expects a "heartbeat" or acknowledgment every 5 seconds, and Chrome delays it by 60 seconds, the connection times out.

The Whitelist Strategy

Most users try to disable throttling globally, which ruins battery life. The correct engineering approach is Selective Persistence.

Granular Control: SuperchargePerformance allows you to say "Maximize battery on these 49 tabs, but give this 1 AI tab 100% CPU priority."

Result: You get the generated code without the "Network Error" and without the dead laptop battery.

FAQ

Why does Chrome kill my ChatGPT tab?

Chrome suspends background tabs to save memory. When you switch away from ChatGPT for more than 5 minutes, Chrome may freeze or discard the tab, breaking the WebSocket connection and losing your conversation context.

How do I keep ChatGPT running in a background tab?

Whitelist chat.openai.com in a tab suspension extension like SuperchargePerformance. This prevents the tab from being suspended while still saving RAM on your other inactive tabs.

Does ChatGPT lose conversation history when Chrome suspends it?

Your conversation history is saved server-side by OpenAI. But the active session — including any unsent messages, streaming responses, or real-time features — is lost when Chrome suspends the tab. You'll need to reload and potentially re-enter your last prompt.

Does this also affect Claude, DeepSeek, and Gemini?

Yes. Any AI chat interface that uses WebSocket or Server-Sent Events (SSE) for real-time streaming has the same problem. Claude (claude.ai), DeepSeek, Google Gemini, and Perplexity all break when Chrome suspends their tab. Whitelist all AI chat domains you use: claude.ai, chat.deepseek.com, gemini.google.com, perplexity.ai.