[Bug]: msedge refuses to start when started with --remote-debugging-pipe #36292
Description
Version
1.52.0
Steps to reproduce
defineConfigwith a project:{ name: "msedge", use: { ...devices["Desktop Edge"], channel: "msedge" } }- Run the test(s)
Expected behavior
The tests run.
Actual behavior
msedge.exe refuses to start.
Additional context
Command playwright tried to run (cmd.exe-ified for repro):
"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --disable-field-trial-config --disable-background-networking --disable-background-timer-throttling --disable-backgrounding-occluded-windows --disable-back-forward-cache --disable-breakpad --disable-client-side-phishing-detection --disable-component-extensions-with-background-pages --disable-component-update --no-default-browser-check --disable-default-apps --disable-dev-shm-usage --disable-extensions --disable-features=AcceptCHFrame,AutoExpandDetailsElement,AvoidUnnecessaryBeforeUnloadCheckSync,CertificateTransparencyComponentUpdater,DeferRendererTasksAfterInput,DestroyProfileOnBrowserClose,DialMediaRouteProvider,ExtensionManifestV2Disabled,GlobalMediaControls,HttpsUpgrades,ImprovedCookieControls,LazyFrameLoading,LensOverlay,MediaRouter,PaintHolding,ThirdPartyStoragePartitioning,Translate --allow-pre-commit-input --disable-hang-monitor --disable-ipc-flooding-protection --disable-popup-blocking --disable-prompt-on-repost --disable-renderer-backgrounding --force-color-profile=srgb --metrics-recording-only --no-first-run --enable-automation --password-store=basic --use-mock-keychain --no-service-autorun --export-tagged-pdf --disable-search-engine-choice-screen --unsafely-disable-devtools-self-xss-warnings --no-sandbox "--user-data-dir=%Temp%\playwright_chromiumdev_profile-JXfNA6" --remote-debugging-pipe --no-startup-windowIf I run this command without --remote-debugging-pipe, msedge.exe appears in the Task Manager and without --no-startup-window I get the GUI to show as well.
When it fails to open, no logs are generated and the exit code is 0, indicating that nothing went wrong.
Output of a test with DEBUG=pw:browser npx playwright test:
[msedge] › tests_playwright\tests\Bars.spec.ts:316:5 › Bars (bitmap check) › Analytics bar
pw:browser <launching> C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe --disable-field-trial-config --disable-background-networking --disable-background-timer-throttling --disable-backgrounding-occluded-windows --disable-back-forward-cache --disable-breakpad --disable-client-side-phishing-detection --disable-component-extensions-with-background-pages --disable-component-update --no-default-browser-check --disable-default-apps --disable-dev-shm-usage --disable-extensions --disable-features=AcceptCHFrame,AutoExpandDetailsElement,AvoidUnnecessaryBeforeUnloadCheckSync,CertificateTransparencyComponentUpdater,DeferRendererTasksAfterInput,DestroyProfileOnBrowserClose,DialMediaRouteProvider,ExtensionManifestV2Disabled,GlobalMediaControls,HttpsUpgrades,ImprovedCookieControls,LazyFrameLoading,LensOverlay,MediaRouter,PaintHolding,ThirdPartyStoragePartitioning,Translate --allow-pre-commit-input --disable-hang-monitor --disable-ipc-flooding-protection --disable-popup-blocking --disable-prompt-on-repost --disable-renderer-backgrounding --force-color-profile=srgb --metrics-recording-only --no-first-run --enable-automation --password-store=basic --use-mock-keychain --no-service-autorun --export-tagged-pdf --disable-search-engine-choice-screen --unsafely-disable-devtools-self-xss-warnings --no-sandbox --remote-debugging-io-pipes=3,4 --user-data-dir=Temp\playwright_chromiumdev_profile-aXHo4Y --remote-debugging-pipe --no-startup-window +0ms
pw:browser <launched> pid=13144 +10ms
pw:browser [pid=13144] <gracefully close start> +22ms
pw:browser [pid=13144] <kill> +0ms
pw:browser [pid=13144] <will force kill> +0ms
pw:browser [pid=13144] taskkill stderr: ERROR: The process "13144" not found.
pw:browser +114ms
pw:browser [pid=13144] <process did exit: exitCode=0, signal=null> +1ms
pw:browser [pid=13144] starting temporary directories cleanup +0ms
pw:browser [pid=13144] finished temporary directories cleanup +558ms
pw:browser [pid=13144] <gracefully close end> +0ms
1) [msedge] › tests_playwright\tests\Bars.spec.ts:316:5 › Bars (bitmap check) › Analytics bar ────
Error: browserType.launch: Target page, context or browser has been closed
Browser logs:
<launching> C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe --disable-field-trial-config --disable-background-networking --disable-background-timer-throttling --disable-backgrounding-occluded-windows --disable-back-forward-cache --disable-breakpad --disable-client-side-phishing-detection --disable-component-extensions-with-background-pages --disable-component-update --no-default-browser-check --disable-default-apps --disable-dev-shm-usage --disable-extensions --disable-features=AcceptCHFrame,AutoExpandDetailsElement,AvoidUnnecessaryBeforeUnloadCheckSync,CertificateTransparencyComponentUpdater,DeferRendererTasksAfterInput,DestroyProfileOnBrowserClose,DialMediaRouteProvider,ExtensionManifestV2Disabled,GlobalMediaControls,HttpsUpgrades,ImprovedCookieControls,LazyFrameLoading,LensOverlay,MediaRouter,PaintHolding,ThirdPartyStoragePartitioning,Translate --allow-pre-commit-input --disable-hang-monitor --disable-ipc-flooding-protection --disable-popup-blocking --disable-prompt-on-repost --disable-renderer-backgrounding --force-color-profile=srgb --metrics-recording-only --no-first-run --enable-automation --password-store=basic --use-mock-keychain --no-service-autorun --export-tagged-pdf --disable-search-engine-choice-screen --unsafely-disable-devtools-self-xss-warnings --no-sandbox --remote-debugging-io-pipes=3,4 --user-data-dir=Temp\playwright_chromiumdev_profile-aXHo4Y --remote-debugging-pipe --no-startup-window
<launched> pid=13144
Call log:
- <launching> C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe --disable-field-trial-config --disable-background-networking --disable-background-timer-throttling --disable-backgrounding-occluded-windows --disable-back-forward-cache --disable-breakpad --disable-client-side-phishing-detection --disable-component-extensions-with-background-pages --disable-component-update --no-default-browser-check --disable-default-apps --disable-dev-shm-usage --disable-extensions --disable-features=AcceptCHFrame,AutoExpandDetailsElement,AvoidUnnecessaryBeforeUnloadCheckSync,CertificateTransparencyComponentUpdater,DeferRendererTasksAfterInput,DestroyProfileOnBrowserClose,DialMediaRouteProvider,ExtensionManifestV2Disabled,GlobalMediaControls,HttpsUpgrades,ImprovedCookieControls,LazyFrameLoading,LensOverlay,MediaRouter,PaintHolding,ThirdPartyStoragePartitioning,Translate --allow-pre-commit-input --disable-hang-monitor --disable-ipc-flooding-protection --disable-popup-blocking --disable-prompt-on-repost --disable-renderer-backgrounding --force-color-profile=srgb --metrics-recording-only --no-first-run --enable-automation --password-store=basic --use-mock-keychain --no-service-autorun --export-tagged-pdf --disable-search-engine-choice-screen --unsafely-disable-devtools-self-xss-warnings --no-sandbox --remote-debugging-io-pipes=3,4 --user-data-dir=Temp\playwright_chromiumdev_profile-aXHo4Y --remote-debugging-pipe --no-startup-window
- <launched> pid=13144
Error Context: test-results\Bars-Bars-bitmap-check-Analytics-bar-msedge\error-context.md
RemoteDebuggingAllowed doesn't appear to be configured, but I put in a ticket to enable it. The docs say that it should work regardless.
If I change --remote-debugging-pipe to --remote-debugging-port=0 manually, then the browser also starts, but I didn't find good documentation on how to make that work with a config file and npx playwright test.
Environment
System:
OS: Windows 11 10.0.22631
CPU: (16) x64 Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz
Memory: 44.68 GB / 63.62 GB
Binaries:
Node: 24.2.0 - C:\Program Files\nodejs\node.EXE
npm: 11.1.0 - C:\Program Files\nodejs\npm.CMD
IDEs:
VSCode: 1.100.3 - C:\Program Files\Microsoft VS Code\bin\code.CMD
Languages:
Bash: 5.2.21 - C:\Windows\system32\bash.EXE
npmPackages:
@playwright/test: ^1.52.0 => 1.52.0