How to Fix an Unresponsive Tab in Chrome ("Page Unresponsive")

The page goes gray, a dialog pops up — "Page Unresponsive: [site name] isn't responding. Wait or Kill page?" — and your cursor clicks land on nothing. It looks like a crash. It isn't.

Unresponsive is not the same as crashed

Chrome's "Aw, Snap!" error means a tab's process died. An unresponsive tab is still very much alive — it's just stuck. Something on the page (usually JavaScript) is running in a tight loop or blocking the main thread, so the tab can't process your clicks, scrolls, or the dialog's own "Wait" button fast enough.

Chrome's hang detector watches for this: if a tab goes quiet for too long, it surfaces the "Page Unresponsive" prompt so you're not left staring at a dead-looking page with no way out.

The distinction matters because the fix is different. A crashed tab just needs a reload. A hung tab often needs to be killed outright, because whatever's looping isn't going to stop on its own.

Fix it: the quick checklist

1. Try "Wait" once, if you triggered something heavy. Uploading a large file, exporting a big document, or running an in-page calculation can look identical to a hang. Give it one shot at finishing.
2. If the dialog reappears, or you didn't trigger anything — kill it. Click "Wait" and getting the same prompt again seconds later means it's genuinely stuck, not just slow.
3. Open Chrome's Task Manager for a cleaner kill. Press Shift+Esc (or Chrome menu → More tools → Task Manager), find the tab by name, and click "End process." This works even if the in-page dialog itself has stopped responding.
4. Reopen it if you need it. Ctrl+Shift+T (Cmd+Shift+T on Mac) reopens the most recently closed tab, landing you back on the same URL without whatever state made it hang.

Why Chrome's Task Manager beats the in-page dialog

The "Page Unresponsive" dialog is rendered by the browser, but it still depends on the tab's process reporting back that it heard you. In a bad enough hang, even clicking "Kill page" can lag or fail to register.

Chrome's own Task Manager (Shift+Esc) works at a different level — it lists every tab and extension as a separate process with live CPU and memory numbers, and "End process" terminates that process directly, the same way your OS's task manager would kill an app. If a tab is bad enough that the dialog itself feels frozen, this is the reliable way in.

It's also the fastest way to spot the problem before it becomes a dialog: sort by CPU, and a tab pegged at 90%+ while sitting in the background is the one about to freeze on you next.

Why the same tab keeps freezing

If it's not a one-off, look at what's specific to that tab:

• A runaway script. Infinite loops, unthrottled animations, or a badly optimized single-page app can pin a CPU core and block input indefinitely. There's nothing to do here except avoid the page or wait for the site to fix it.
• Too much rendered at once. A spreadsheet with tens of thousands of rows, a chat thread with years of history, or an infinite-scroll feed that never virtualizes can overwhelm the render thread as it grows.
• A conflicting extension. Extensions inject code into every page they have access to. One that's buggy or doing heavy work on page load can freeze pages that would otherwise be fine.

To isolate an extension as the cause: open the page in an Incognito window (extensions are off there by default unless you've explicitly allowed them). If it stays responsive, re-enable your extensions one at a time in a normal window and revisit the page to find the culprit.

The part a kill-and-reopen can't fix

Ending the process gets your browser back, but it doesn't preserve what was on the page — a half-written comment, an unsaved form, your scroll position in that giant thread. Chrome doesn't checkpoint any of that before it kills the process.

And if the tab that froze was one of a dozen you had open around the same task, losing track of the others while you deal with the freeze is often the bigger cost.

Amazing Tabs makes "save first" the default so a frozen tab is never a surprise:

• Save a tab or a whole window in one click, before it's the one that hangs — so a killed process is never your only copy of what you were doing.
• Press / to search everything you've saved by title or content, instead of trying to remember exactly what was open when the freeze happened.
• Saved tabs live independently of the live browser state — a save doesn't care whether the original tab froze, crashed, or is still sitting there stuck.
• Free for up to 100 saved links, so building the habit costs nothing.

Stop losing your place to a frozen tab. Add Amazing Tabs to Chrome — free, no signup. Save your open tabs once, and a hang on any of them stops costing you anything.

Quick recap

• "Page Unresponsive" means a stuck script, not a dead process — different from "Aw, Snap!," and it needs a different fix.
• Wait once if you triggered something heavy; kill it if the dialog repeats or nothing explains it.
• Shift+Esc opens Chrome's Task Manager for a reliable kill when the in-page dialog itself is lagging.
• Recurring freezes on one page point to a runaway script, an overloaded render, or a conflicting extension — test in Incognito to rule extensions in or out.
• A kill-and-reopen doesn't save what was on the page — save what matters before it's the tab that hangs, not after.

Further reading: How to Fix a Crashed Tab in Chrome ("Aw, Snap!") for when the tab dies outright instead of hanging, Why Chrome Uses So Much Memory if freezes are showing up alongside a generally sluggish browser, or Chrome Tab Won't Close? Here's How to Fix It if the close button itself is the thing not responding.

Add Amazing Tabs to Chrome — free → Install from the Chrome Web Store. 100 saved links free, upgrade only if you want unlimited and cross-device sync. See pricing for the full breakdown — including the $99 lifetime deal (capped at 200 spots).