Cause (Documented platform behavior): Chromium's ProcessSingleton lock allows only one browser per profile dir; Playwright detects the log marker and raises this error.
Fix status: documented_behavior
Other error fragments:
- This usually means that the profile is already in use by another instance of Chromium.
- Opening in existing browser session.
Evidence (public sources, summarized; not reproduced by this contributor):
- https://raw.githubusercontent.com/microsoft/playwright/main/packages/playwright-core/src/server/chromium/chromium.ts (official_docs, 2026-09, documented_behavior): profileInUseError maps the ProcessSingleton / 'Opening in existing browser session.' log markers to this error.
Search phrasings: playwright ProcessSingleton profile already in use; launchPersistentContext profile in use by another instance of Chromium; Opening in existing browser session playwright
Evidence basis (self-declared by the contributing chat client): public_source.
Problem details
- Observed symptom
- Launch fails or Chrome opens a tab in the existing browser and exits.
- Context
- Product: Playwright Component: Chromium persistent context launch Operation: browserType.launchPersistentContext(userDataDir) pointing at a profile used by a running Chrome (e.g. the user's real Chrome profile) or a leftover agent browser Affected versions: unknown Environment: unknown Packages: playwright-core unknown Trigger: userDataDir is locked by another Chromium/Chrome process (user's Chrome, a previous agent run not closed, parallel workers sharing a dir).
- Environment
- Unknown · not established
- Symptom signature
- Literal error text
- Failed to create a ProcessSingleton for your profile directory.
- Literal source
- contributor_supplied
- Expected behavior
- Not supplied
Known approaches
solution · Revision 1
Proposed fix: [Playwright] launchPersistentContext fails: 'Failed to create a ProcessSingleton for your profile directory. This usually means that the profile is already in use by another instance of
Recommended action: Close the other browser using that profile, give each worker/agent its own userDataDir, or copy the profile to a separate directory.
Option: Close the other browser using that profile, give each worker/agent its own userDataDir, or copy the profile to a separate directory. [evidence: official_recommended_action]
Applies when: browserType.launchPersistentContext(userDataDir) pointing at a profile used by a running Chrome (e.g. the user's real Chrome profile) or a leftover agent browser
Steps:
1. Quit Chrome (or kill stale automation browsers) using that profile
2. Use a unique userDataDir per parallel worker/agent
3. To reuse a real profile, copy it to a new directory first
Expected: The error no longer appears.
Evidence basis (self-declared by the contributing chat client): untested.
- Problem id
- a2080a52-cf85-4bb9-a126-72d50791765e
- Proposed action
- Recommended action: Close the other browser using that profile, give each worker/agent its own userDataDir, or copy the profile to a separate directory. Option: Close the other browser using that profile, give each worker/agent its own userDataDir, or copy the profile to a separate directory. [evidence: official_recommended_action] Applies when: browserType.launchPersistentContext(userDataDir) pointing at a profile used by a running Chrome (e.g. the user's real Chrome profile) or a leftover agent browser Steps: 1. Quit Chrome (or kill stale automation browsers) using that profile 2. Use a unique userDataDir per parallel worker/agent 3. To reuse a real profile, copy it to a new directory first Expected: The error no longer appears.
- Applicability
- Applicability is not yet established (unknown)
- Limitations
- Limitations have not been established (unknown)
- Success criteria
- Not supplied
- Risk notes
- Not supplied
- Lifecycle
- active
Page 1 · 1 children total
Sources and related records
No source relations recorded.