Chrome: Page Unresponsive — The following page(s) have become unresponsive. You can wait for them to become responsive or exit the page(s)
A tab is stuck in a busy loop or waiting on something heavy, so Chrome offers to wait or kill it.
Page UnresponsiveThe following page(s) have become unresponsiveWait or Exit pages Meaning
The tab's JavaScript is blocking the main thread — an infinite loop, a huge synchronous task, a runaway extension, or a page loading enormous data. If you are the developer, record a Performance profile and break long tasks into chunks (requestIdleCallback, Web Workers).
Common causes
- Infinite or very long synchronous JavaScript loop
- Huge DOM/table rendering or layout thrashing
- Memory pressure or too many tabs
- Faulty extension or content script
- Heavy page on an old device
⚡ Quick fix
- Click "Exit pages" or wait a few seconds
- Reload with extensions disabled
- Developers: profile in DevTools → Performance and split long tasks
Detailed fix by platform
JavaScript
- Break long loops: process 1,000 items per tick using
setTimeout/requestIdleCallback, or move work to a Web Worker
Chrome
- Press Shift+Esc to open Chrome's Task Manager and end the heavy tab/extension
How to diagnose
- Which — Which tab/extension uses most CPU (Shift+Esc)?
- Reproduce — Only on one page?
- Profile — Long task in DevTools?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- Aw, Snap! Chrome: Aw, Snap! Something went wrong while displaying this webpage. Error code: STATUS_ACCESS_VIOLATION / SIGILL / Out of Memory
- captive portal Browser: This network requires you to sign in — captive portal (hotel, airport, café Wi-Fi) blocking HTTPS sites
- DevTools failed to load source map DevTools: Failed to load source map — Could not load content for https://…/app.js.map: HTTP error: status code 404
Most viewed in Browser
Other ways to find it
Where this error sits
Origin: On your device. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 15 Oct 2026