Gemini AI Crashing Chrome? 5 Fixes That Work (2026)

A confirmed memory leak in Chrome’s Gemini UI (Chromium issue 468317754) causes DOM nodes to accumulate without garbage collection. Users report extended Gemini sessions pushing a single tab past 1 GB RAM before Chrome crashes.

Key takeaways

• A Gemini tab that starts around 200 MB grows with every prompt and Chrome won’t warn you before the crash.
• Gemini auto-browse in Chrome 147 spawns background processes for every page it reads, multiplying memory pressure fast.
• Suspending background tabs before generating large outputs frees the renderer memory Gemini needs — the single most effective fix.

Your Chrome froze mid-sentence. Gemini was generating a long response — code, an explanation, then more code — and somewhere around the third or fourth section the browser locked up. Task Manager showed 6+ GB of RAM gone. Then the GPU process crashed, and Chrome took everything with it.

This is not a random crash. The Gemini tab was growing the entire session — every response added DOM nodes that never got cleaned up. The longer you kept the conversation going, the more memory it consumed. Add auto-browse — which Chrome 147 ships for AI Pro and Ultra subscribers — and you had background processes stacking on top of an already leaky foreground tab.

The fixes below are ranked by how much memory they actually recover.

What the Gemini Memory Leak Actually Does

When Gemini generates output — text, code blocks, tables, images — Chrome renders each piece as DOM nodes in the tab’s renderer process. Normal pages discard DOM nodes when content is replaced or you navigate away. Gemini does neither: responses accumulate in a single long page. Each follow-up prompt adds more nodes. The confirmed bug is that these nodes are never garbage collected while the tab remains open.

Result: a Gemini tab that started around 200 MB can climb past 1 GB after an extended session — users report reaching 1.5 GB or more. On machines with 8 GB RAM, that alone can push Chrome into memory pressure territory. On machines with 16 GB but 20+ tabs open, the Gemini tab’s growth tips the balance.

The GPU process crash is a secondary effect. Chrome offloads rendering to the GPU process. When system RAM is exhausted, Chrome can no longer service GPU memory requests, the GPU process crashes, and Chrome interprets this as a fatal error — taking all open tabs with it.

Fix 1: Suspend Background Tabs Before Running Gemini

This recovers the most memory. Chrome’s renderer process for each tab holds the tab’s full DOM, JavaScript heap, and cached resources in memory. An inactive tab with a complex web app open — Figma, Notion, Google Sheets — can hold 300–800 MB by itself.

Before starting a long Gemini session, suspend those background tabs. Suspended tabs release their renderer process entirely. That memory becomes available to the Gemini tab’s growing DOM.

Manual path: Press Shift + Esc to open Chrome Task Manager. Click the Memory column to sort descending. Note which tabs are using the most RAM. Select them and click End Process. Chrome will show a “Tab was discarded” message when you return to them — they reload on demand.

Automated path: SuperchargePerformance uses chrome.tabs.discard() to automatically suspend tabs that have been inactive past a configurable threshold. Inactive tabs are discarded in the background — you do not lose them, they just reload when you click back. With 20 tabs open, this typically frees 1–3 GB before Gemini even starts generating.

The extension also has 14 auto-protected apps (Google Docs, Gmail, Sheets, Calendar, and others) that are never suspended — you lose no active work.

Fix 2: Break Long Gemini Sessions into Smaller Chunks

Every response Gemini generates adds to the same DOM without cleanup. A session with 10 long responses has approximately 10× the memory footprint of one response.

The workaround: close the Gemini tab periodically and open a fresh one. This forces a full garbage collection and renderer process restart. You lose the conversation history in the tab, but you keep your system stable.

Concretely:

• For research sessions generating multiple long outputs, open a new Gemini tab every 3–4 prompts.
• For code generation that produces large outputs, break the task into separate conversations instead of one continuous thread.
• Close the Gemini side panel when not actively using it — the side panel Gemini integration keeps a renderer process alive even when hidden.

This is tedious. It is also the only workaround that directly addresses the leak mechanism itself.

Fix 3: Monitor Gemini Tab Memory in Real Time

You can watch the RAM climb and intervene before Chrome reaches crisis. Chrome Task Manager (Shift + Esc) shows per-process memory. Sort by Memory and watch the Gemini renderer process row during a session.

A practical threshold: if the Gemini tab crosses 800 MB in Task Manager, close it and open a fresh one before continuing.

SuperchargePerformance’s RAM dashboard uses the chrome.processes API to show real-time per-tab memory with color-coded warnings. The Gemini tab appears as its own row — the dashboard updates live so you can see the progressive growth rather than discovering it at crash time.

Fix 4: Disable Auto-Browse If You Do Not Need It

Chrome 147’s auto-browse feature lets Gemini read web pages as part of its response. Each page it reads opens a background process. That is fine for one or two pages. For a research task where Gemini browses 8–10 URLs, it is 8–10 background renderer processes stacked on top of the leaky foreground Gemini tab.

Auto-browse is available only for AI Pro and AI Ultra subscribers on Chrome 147 on macOS, Windows, and ChromeOS. If you are in this group and seeing frequent crashes, this is the first setting to toggle off.

Disable it: open Gemini in Chrome → Settings (gear icon) → toggle Auto-browse off. Use it only when you specifically need deep research responses and your machine has enough headroom.

If your crashes started after Chrome 147 updated and you have an AI Pro or Ultra subscription, auto-browse is almost certainly the compounding factor.

Fix 5: Lower the Baseline Memory Load

Even before the Gemini tab opens, Chrome is carrying memory load from every page already open. Ad networks, tracking pixels, and analytics scripts inject JavaScript into every tab you have open — these scripts stay in memory as long as the tab is alive.

Blocking these requests before they load reduces the baseline memory footprint across all your open tabs. Less background noise means more headroom for Gemini’s expanding DOM.

SuperchargePerformance applies 186,000+ declarative net request rules from 22 sources across three tiers — ads, trackers, and telemetry. On a typical browser with news sites, social media, and SaaS tools open, blocking cuts 40–150 MB of injected script memory per session. That is not the primary fix for Gemini crashes, but it is persistent headroom that costs nothing to maintain.

The rules run at the network level via Chrome’s declarative net request API — no per-request processing, no CPU overhead, no telemetry.

Which Fix to Start With

The answer depends on what the crash looks like:

• Chrome crashes mid-Gemini response with many tabs open? Fix 1 — suspend background tabs first.
• Gemini session progressively slows over time before crashing? Fix 2 — break into smaller sessions.
• Crashes started with Chrome 147 and AI Pro/Ultra subscription? Fix 4 — disable auto-browse.
• Want to see the problem coming before it crashes? Fix 3 — real-time RAM monitoring.
• Crashes happen even with few tabs open? Fix 5 reduces baseline load, but the real issue may be hardware — under 8 GB RAM, Gemini sessions are inherently unstable with the current leak.

If you are on 8 GB RAM, suspending background tabs (Fix 1) and monitoring RAM (Fix 3) together give you the best chance of stable Gemini sessions. Google has not patched the underlying leak as of March 2026 — the workarounds are the only option until a fix ships.

Quick Setup

Install SuperchargePerformance from the Chrome Web Store — free, no account needed. Open the popup and check your current RAM usage. Then start a Gemini session and watch the dashboard as the tab grows. You will see the problem in real time, and the extension will keep your other tabs from making it worse.

For related memory issues, see Fix Chrome High Memory Usage and Fix Chrome Out of Memory Errors.