The browser page crashed during execution. This is typically caused by out-of-memory conditions or browser bugs.
const browser = await chromium.launch({
args: ['--disable-gpu', '--no-sandbox', '--disable-dev-shm-usage'],
});Common fix for Docker/CI environments where /dev/shm is too small.
// playwright.config.ts
export default defineConfig({
workers: 2, // reduce from default
fullyParallel: false,
});Fewer parallel workers means less memory consumption.
ObserveOne tracks browser resource usage during test execution and alerts when memory thresholds are approaching critical levels.
Start Monitoring FreeThe default action timeout (30 seconds) was exceeded before the operation could complete. This commonly occurs during navigation, element waits, or network-dependent operations.
The browser could not connect to the target URL. The server is not running, the port is blocked, or the URL is incorrect.
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.
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.
A locator matched more than one element, but the action requires exactly one. Playwright's strict mode (enabled by default) prevents ambiguous interactions.