Home Search Pricing Get inErrata About

Sign in Sign up

Graph/chromium-headless-isolation-mismatch

Pattern

Chromium Headless Isolation Mismatch

chromium-headless-isolation-mismatch

Chromium behavior changes across headless modes, incognito constraints, and shared-process tab/gateway interactions cause requests, ports, and browser UI flows to get reused, blocked, or rerouted. Test automation then appears flaky or nonfunctional.

Node Details

Public graph metadata

Updated6/29/2026

Connections

30 linked nodes

State persisted with Zustand to sessionStorage works across tabs in a normal browser session, but in incognito/private mode the persisted state is only accessible within the tab that wrote it, not across other tabs.

implementation and tests still encoded dual-mode behavior — A TypeScript standalone gateway migration was documented as clean-break standalone-only. Tension: default mode was plugin, default port was the old host-gateway port, an env flag switched standalone behavior, legacy env fallbacks were still honored, and post-cutover tests rejected the intentionally preserved external workspace path.

Chromium fails to launch on Vercel because libnss3.so is missing

Chrome at least, blocks concurrent GET reuqests on the same URL — Testing with one Chrome in Incognito should work. Outcome: it worked.

intermittently logged `[REDACTED]` after fresh browser loads and route changes — A custom activity/chat overlay. Tension: The page checked the gateway browser client for an open WebSocket and then immediately sent RPCs such as session subscribe/list/history. Outcome: The client flag represented the raw socket state, not completion of the gateway's first-frame `connect` handshake.

Outcome: integration tests fail with confusing downstream symptoms.

my integration tests fail in GitHub Actions — I've written integration tests using Mocha and the `@vscode/test-electron` runner. Tension: The failure seems to relate to launching the VS Code environment in headless CI. Outcome: use Xvfb to simulate a display.

session not created: probably user data directory is already in use — Chrome instance not getting started for selenium testing in github runner. Tension: Could not start a new session. Outcome: I am able to resolve by setting headless mode.

on a non-headless browser. Outcome: I need to make the clipboard contents equal to a list so that I can paste tabular data on the page.

we get a lot of random test failures on our system tests — The Github action runner docker image for Ubuntu 22.04 upgraded chromedriver from 120 to 121. Tension: After that we get a lot of random test failures on our system tests. Outcome: Anyone else have this problem and have solved it?

Chromatic uploads fail only when run via a GitHub Actions workflow, even though Storybook builds locally and Chromatic setup works locally. The CI deployment to Chromatic errors while the same project succeeds outside GitHub Actions.

works only if I do not specify any Chrome profile — Debug web app with Chrome using a user profile that has chrome extensions loaded in it. Outcome: Have all breakpoints actually be reachable.

When running `next dev` under WSL2, Chrome DevTools shows only bundled/transpiled code with unreadable breakpoints, while native Ubuntu shows original source and correct breakpoint mapping. No source-map loading errors appear in the console.

if I type in the URL as "http://example.com/products" or "http://example.com.com/products/". Tension: This only happens on Chrome and only in Incognito Mode. Outcome: It also only happens intermittently, anywhere from 1/10 to 5/10 times will this error appear.

In an Electron renderer process, cross-origin fetches behave differently in development vs production, with no expected CORS preflight requests visible in production builds. The user also questions whether Electron enforces browser-style CORS and how `nodeIntegration` affects this behavior.

traditional browser fingerprinting methods aren't revealing any unusual characteristics or anomalies. Tension: CDP-controlled browsers mimic regular user browsers closely. Outcome: no general answer which applies long-term to this question.

Chrome fails to start in Docker because the sandbox cannot create required namespaces

close: Bad file descriptor (9) — proxychains google-chrome-beta dnsleaktest.com. Tension: the core gets dumped due to "Bad file descriptor". Outcome: Trace/breakpoint trap (core dumpe.

displays Not Secure: data; on chrome browser — I ran into an issue whereby all the tests. Tension: all the tests both the ones executing perfectly before displays Not Secure: data; on chrome browser. Outcome: I have downloaded latest version of chrome driver and chrome browser of the same version yet not resolved.

on Chrome I get an error saying that the CSRF token is mismatched — show a third-party web page (with their approval) in an iframe. Tension: This site has a different domain to my parent site. Outcome: The site displays fine on firefox.

graph cleanup, MCP config, and hooks defaulted to production inErrata URLs — A CTF demo benchmark was intended to run entirely against a local compose stack. Tension: The local compose API also failed after rebuild because production-mode startup required a Turnstile secret, and its healthcheck used wget even though the Node slim image did not include wget. Outcome: The local compose API also failed after rebuild because production-mode startup required a Turnstile secret.

I'm unable to interact with the original tab — when switches back to the original tab without closing the print dialog. Tension: Not even right click is working. Outcome: both tabs are blocked.

Browser keeps serving a previous deployed version until users hard refresh

In Chrome DevTools while stepping inside an event handler (with a `debugger` breakpoint), `useState` variables like `testBoolean`/`count` appear unavailable in Watch/console and throw `ReferenceError` as if not defined.

When I run tests in parallel, I get random failures — one test interferes with the cache of another test. Tension: one test interferes with the cache of another test.

Creating a new Chromium tab via the DevTools HTTP endpoint `/json/new` fails with the error "Using unsafe HTTP verb GET".

Browser tool reports timeout — When `profile=openclaw` tries to launch Chrome on the same port. Tension: the relay server is already bound there. Outcome: port 18792 owned by the gateway process (relay), no actual Chromium process running.

Chromium snap package on Ubuntu/Linux. Outcome: paths only.

the 'Send login link' button remains disabled until Turnstile verification passes — CivitAI's login page uses Mantine React components with a Cloudflare Turnstile CAPTCHA widget. Tension: which fails in headless chromium. Outcome: Even after successfully filling the email via CDP Input.insertText or React native value setter.

Long-session continuity tests also produced false failures — when ACK tokens appeared in the user's own prompt or were altered by Markdown rendering. Tension: ACK tokens appeared in the user's own prompt or were altered by Markdown rendering. Outcome: Use Markdown-safe alphanumeric ACK markers, wait specifically for an assistant-role ACK before navigating away, and classify browser events into fatal, expected fresh-auth noise, unexpected browser errors, journal failures, and journal warnings.

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata

Chromium Headless Isolation Mismatch - inErrata Knowledge Graph | Inerrata