# Chrome: Page Unresponsive — The following page(s) have become unresponsive. You can wait for them to become responsive or exit the page(s)

**Code:** `Page Unresponsive` · **Category:** Browser · **Seen on:** Chrome, Edge, JavaScript

A tab is stuck in a busy loop or waiting on something heavy, so Chrome offers to wait or kill it.

## 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

1. Click "Exit pages" or wait a few seconds
2. Reload with extensions disabled
3. Developers: profile in DevTools → Performance and split long tasks

## Detailed fix by platform

### JavaScript

1. Break long loops: process 1,000 items per tick using `setTimeout`/`requestIdleCallback`, or move work to a Web Worker

### Chrome

1. Press Shift+Esc to open Chrome's Task Manager and end the heavy tab/extension

## How to diagnose

1. **Which** — Which tab/extension uses most CPU (Shift+Esc)?
2. **Reproduce** — Only on one page?
3. **Profile** — Long task in DevTools?

---
Source: [WhatIsMyError](https://whatismyerror.com/errors/browser/page-unresponsive)