high

Error: browser has been closed

An operation was attempted on a browser or page that has already been closed. This often happens in afterEach hooks or when tests share browser instances incorrectly.

Common Causes

  1. 1Test cleanup closed the browser before other tests finished
  2. 2browser.close() called in afterAll while tests are still running
  3. 3Unhandled exception in one test caused browser to close, affecting subsequent tests
  4. 4Using a shared browser instance across test files

How to Fix

Use Playwright's built-in fixtures

// Use the built-in 'page' fixture — Playwright manages lifecycle
test('my test', async ({ page }) => {
  await page.goto('/');
  // page is automatically created and destroyed per test
});

Playwright's test fixtures handle browser lifecycle automatically. Avoid manual browser management.

How ObserveOne Helps

ObserveOne manages test environments and ensures clean browser lifecycle management across your test suite.

Start Monitoring Free

Related Errors

net::ERR_CONNECTION_REFUSED

The browser could not connect to the target URL. The server is not running, the port is blocked, or the URL is incorrect.

Error: page.goto: Page crashed!

The browser page crashed during execution. This is typically caused by out-of-memory conditions or browser bugs.

TimeoutError: Exceeded 30000ms

The default action timeout (30 seconds) was exceeded before the operation could complete. This commonly occurs during navigation, element waits, or network-dependent operations.

TimeoutError: page.goto: Timeout 30000ms exceeded

Navigation to the target URL did not complete within the timeout period. The page either failed to respond or took too long to reach the 'load' event.

TimeoutError: waiting for selector

Playwright waited for an element matching the given selector but it did not appear within the timeout. The element may not exist, may be hidden, or may appear under a different selector.