-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Chromium on Windows does not launch without --no-sandbox #3191
Comments
More info from @yingzhe who was running into this: this happens when Chromium is launched with admin privileges. Running without admin does not require the --no-sandbox flag. Confirmed with the other user who was faced this as well: their VS Code was running as admin, and they were launching Chromium via @aslushnikov: Can we handle this case? Seems similar to root user on Linux? |
It may have something to do with launching from VS Code, |
@arjun27 I couldn't reproduce this: tried running under administrator in both MINGW and CMD terminals and launching simple script there - worked fine for me without |
Playwright: 1.2.1 Below is the error I get when running from non-admin mode command prompt:
Code is the same as what was originally posted by @arjun27 above. I had to interrupt with ctrl+c, as the process never completes. |
@yingzhe can you please try with the latest Playwright v1.3.0? We have some nice logic there to detect missing libraries; I hope it will give us a hint on what's going on. |
I updated Playwright to v1.3.0 but it looks like the error I get is still the same, with the process being stuck forever until I kill it. |
Sandbox configuration proved to be painful in various environments, and this issue is another example. |
Context:
Code Snippet
Describe the bug
Chromium does not launch unless passed with
args: ['--no-sandbox']
- in both headful and headless modes.--disable-gpu
did not help, like in #2698. Logs seen without args are pasted below."method":"Inspector.targetCrashed"
seems to be the culprit.The text was updated successfully, but these errors were encountered: