[Bug]: chromium Error: browserType.launch: spawn EPERM

[aniketicloud]

Version

1.42.1

Steps to reproduce

Node 20.9.0

1. run this in terminal->npm create vite@latest --template react-swc-ts
2. run this in terminal-> npm init playwright@latest
3. select all default options like install browsers location etc
4. npx playwright test

Expected behavior

I expect to run test on chromium with default instructions

Actual behavior

1. [chromium] › example.spec.ts:3:1 › has title ──────────────────────────────────────────────────

   Error: browserType.launch: spawn EPERM
   Call log:

   • C:\Users\aniket.pandharabale\AppData\Local\ms-playwright\chromium-1105\chrome-win\chrome.exe
     --disable-field-trial-config --disable-background-networking --enable-features=NetworkService,NetworkServiceInProcess --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=ImprovedCookieControls,LazyFrameLoading,GlobalMediaControls,DestroyProfileOnBrowserClose,MediaRouter,DialMediaRouteProvider,AcceptCHFrame,AutoExpandDetailsElement,CertificateTransparencyComponentUpdater,AvoidUnnecessaryBeforeUnloadCheckSync,Translate,HttpsUpgrades,PaintHolding --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 --headless --hide-scrollbars --mute-audio --blink-settings=primaryHoverType=2,availableHoverTypes=2,primaryPointerType=4,availablePointerTypes=4 --no-sandbox --user-data-dir=C:\Users\ANIKET~1.PAN\AppData\Local\Temp\playwright_chromiumdev_profile-Z2TfjL --remote-debugging-pipe --no-startup-window

Additional context

No response

Environment

System:
    OS: Windows 10 10.0.19045
    CPU: (8) x64 Intel(R) Core(TM) i5-8265U CPU @ 1.60GHz
    Memory: 4.65 GB / 15.75 GB
  Binaries:
    Node: 20.9.0 - C:\Program Files\nodejs\node.EXE
    npm: 10.1.0 - C:\Program Files\nodejs\npm.CMD
  IDEs:
    VSCode: 1.87.2 - C:\Users\aniket.pandharabale\AppData\Local\Programs\Microsoft VS Code\bin\code.CMD
  Languages:
    Bash: 5.2.15 - C:\Users\aniket.pandharabale\AppData\Local\Programs\Git\usr\bin\bash.EXE
  npmPackages:
    @playwright/test: ^1.42.1 => 1.42.1

[aniketicloud]

The same error happens to me when I run npm init playwright@latest in an empty folder. Playwright asks me to select TS or JS. I select TS. But chromium is failing, other browsers can run tests.

[aniketicloud]

Also, this is a company laptop. One can suggest me like if there are any policies that I should check to run this.
We are choosing Playwright for E2E and component testing.

[yury-s]

The same error happens to me when I run npm init playwright@latest in an empty folder.

It definitely has something to do with the corp policies/antimalware running on your computer. Are you able to launch Chromium from the logged location manually?

[aniketicloud]

The same error happens to me when I run npm init playwright@latest in an empty folder.

It definitely has something to do with the corp policies/antimalware running on your computer. Are you able to launch Chromium from the logged location manually?

Do you mean open the location and open the chromium browser?

[yury-s]

I mean launching C:\Users\aniket.pandharabale\AppData\Local\ms-playwright\chromium-1105\chrome-win\chrome.exe (with --user-data-dir= pointing to an empty dir, so that it starts with a fresh profile).

[Sanjeewahsp]

Hi, I am having same issue with latest node/playwright.

$ npx playwright test
Running 1 test using 1 worker

1. [Mobile Chrome] › login.spec.ts:10:5 › Success login test ─────────────────────────────────
   Error: browserType.launch: spawn EPERM
   Call log:
   • C:\Users\xxxxxxxxxx\AppData\Local\ms-playwright\chromium-1105\chrome-win\chrome.exe --disable-field-trial-config --disable-background-networking --enable-features=NetworkService,NetworkServiceInProcess --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=ImprovedCookieControls,LazyFrameLoading,GlobalMediaControls,DestroyProfileOnBrowserClose,MediaRouter,DialMediaRouteProvider,AcceptCHFrame,AutoExpandDetailsElement,CertificateTransparencyComponentUpdater,AvoidUnnecessaryBeforeUnloadCheckSync,Translate,HttpsUpgrades,PaintHolding --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
     --headless --hide-scrollbars --mute-audio --blink-settings=primaryHoverType=2,availableHoverTypes=2,primaryPointerType=4,availablePointerTypes=4 --no-sandbox --user-data-dir=C:\Users\XXXX~1.SAM\AppData\Local\Temp\playwright_chromiumdev_profile-OkGFpy --remote-debugging-pipe --no-startup-window

1 failed
[Mobile Chrome] › login.spec.ts:10:5 › Success login test ──────────────────────────────────

To open last HTML report run:

npx playwright show-report

$ node -v
v20.11.1

$ npx @playwright/test --version
Version 1.42.1

see the chrome file permission

[pavelfeldman]

@Sanjeewahsp same question to you: #30058 (comment)

[Sanjeewahsp]

@pavelfeldman, I got 'Access is denied' from chrome.exe.

Is this issue(Error: browserType.launch: spawn EPERM) related to permission problem? Or existing chrome browser version issue.
I have latest chrome 123.0.6312.59

[pavelfeldman]

@Sanjeewahsp so your organization won't let Playwright run Chromium installation on your machine. There isn't much we can do about it.

[Sanjeewahsp]

@pavelfeldman, Thank you for the update....

[pavelfeldman]

Closing as per above, please feel free to open a new issue if this does not cover your use case.

[aniketicloud]

I also checked. The issue seems to be related with only Company laptop. Some policy I think is restricting the browser. I checked it with 3 different company laptops and 2 personal laptops.
I think there should be a proper guide on how to use Docker for E2E, component testing, report generation using shards.

[aniketicloud]

At least we have a record for next developers. Thank you very much everyone.