-
Notifications
You must be signed in to change notification settings - Fork 73
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
WebDriverError: unknown error: Chrome failed to start: crashed. (unknown error: DevToolsActivePort file doesn't exist) #214
Comments
Could you retry the test suite with vscode 1.50.0 or older? And did you by any chance introduce webpack or gulp recently? |
I've also added a launch argument to chromedriver that should help in some situations. It might not be enough, but it shouldn't hurt. Feel free to try it out in the new micro version. |
No |
Can you point to the launch argument and explain where to add it please? Note that it doesn't happen all the time. It is random. |
It gets passed to chromedriver by extester, there is nothing for you to do. Just FYI, it's |
it is still happenning: |
I am also facing the same error but only in WSL environment. In mac, it is working fine. Are there any fixes/workarounds found in the meantime? |
up. This issue is still occuring several times per week. |
As discussed in #52 , it looks like on some CI systems chromedriver will have trouble launching if the binary is located on a sufficiently long path (and they don't need to be all that long for it to happen). It actually looks like a single path segment can make a difference. Storing the test resources on a shorter path might help you here. There is a flag to specify just that |
in #52 , if I understand well, the failure appears all the time, not randomly. (issue is still happening from time to time, for instance https://app.circleci.com/pipelines/github/jboss-fuse/vscode-atlasmap/501/workflows/feef7a96-a475-437f-a233-ed1f15ad1a24/jobs/609 ) |
Indeed this is a different issue than #52 . From the info I could find around the internet, the root cause is running chrome(driver) as a root user or using sudo. Are you by chance running any of the commands using |
I'm sure that it is not using sudo. I do not think that it is the root user. i tis the user provided by the default image of Circle CI. |
The same: Launching browser...
0 passing (228ms)
Waiting for the debugger to disconnect... |
Repro'd this by passing a relative path argument |
I am also experiencing this issue(tried on v4.3.0 and v5.2.1). Has anybody found a solution? I am running this in a github action linux runner: I am getting essentially the same output:
|
What are you passing this argument to? |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
experiencing the same issue, except it
ci run: https://github.com/metalbear-co/mirrord/actions/runs/5204141829/jobs/9388134176 |
Duplicates #485 |
We are currently facing some errors in our build:
(unknown error: DevToolsActivePort file doesn't exist)
TypeError: Cannot read property 'manage' of undefined
Please see the error ouput below. It does not happen on every build.
See also https://app.circleci.com/pipelines/github/jboss-fuse/vscode-atlasmap?branch=pull%2F514
The text was updated successfully, but these errors were encountered: