Why an AI chat freezes or crashes your browser tab
Short answer: the tab has run out of memory, because a long conversation — most often a ChatGPT or Claude chat full of code — builds a page bigger than the browser can hold. Copy any unsent text, close other tabs, reload, and do not scroll back to the top.
The tab stops responding. The fan spins up. Sometimes Chrome offers to kill the page entirely. This is not the assistant failing — it is the tab running out of room.
What "out of memory" actually means here
A browser tab has a memory budget. Every message in a conversation consumes some of it: the text, the layout data, the syntax-highlighted code, the rendered images, the undo state of the input box. A very long conversation with a lot of code can reach hundreds of megabytes on its own.
When the tab approaches its ceiling the browser starts working much harder to find room, which is what you feel as the freeze. Cross it and the process is killed — the "Aw, snap" page.
The three things that push it over
- Length plus code. A hundred short messages is fine. Forty messages containing large files is not. Syntax highlighting creates a separate element per token, so one pasted file can cost more than fifty ordinary messages.
- Images in the conversation. Generated and uploaded images stay decoded in memory while they are near the viewport.
- Everything else you have open. The budget is shared across the browser. A chat that behaves alone will crash when it is competing with forty tabs and a video call.
Getting out of it right now
- Do not reload yet if you have unsent text. Select it and copy it first — a reload loses the input box.
- Close other tabs before reloading. Reloading into the same memory pressure just repeats the crash.
- Reload. Most chat sites mount only the recent part of a conversation on a fresh load, so the tab comes back much lighter.
- Do not scroll to the top afterwards. Scrolling back is what re-mounts everything and rebuilds the problem.
Preventing it
Link or attach large files rather than pasting them inline. Start a new conversation when one crosses a few hundred messages — carrying the conclusions across rather than the transcript. And keep an eye on total browser memory if you habitually run many tabs.
The deeper fix is for off-screen messages to stop costing what on-screen ones cost, which is what a speed engine does — and, unlike closing the conversation, it does not ask you to give anything up. The mechanism in detail.
Common questions
Why does ChatGPT crash my browser tab?
The tab ran out of memory. A long conversation with large code blocks and images can reach hundreds of megabytes, and past the tab's limit the browser stops it.
How do I fix a frozen or "Aw, Snap" tab on a long AI chat?
Copy any unsent text first, close other tabs, then reload. Do not scroll back to the top afterwards: that loads every old message again and rebuilds the problem.
Do Claude and Gemini freeze on long chats too?
Yes. Every chat site draws the conversation as one growing page, so a long chat full of code can slow down and freeze on any of them.