Error: DevToolsActivePort file doesn't exist
See original GitHub issueI’m attempting to build and run a docker container for end to end testing of my electron app. I’m receiving the following error:
Failed to create session.
unknown error: Chrome failed to start: exited abnormally.
(unknown error: DevToolsActivePort file doesn't exist)
(The process started from chrome location /app/node_modules/spectron/lib/launcher.js is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
at Object.startWebDriverSession (node_modules/webdriver/build/utils.js:34:15)
Has anyone run into this and found a solution?
Issue Analytics
- State:
- Created 2 years ago
- Reactions:17
- Comments:10
Top Results From Across the Web
unknown error: DevToolsActivePort file doesn't exist while ...
As per my observation DevToolsActivePort file doesn't exist is caused when chrome is unable to find its reference in scoped_dirXXXXX folder.
Read more >Troubleshooting DevToolsActivePort file doesn't exists
TestProjects support Chrome versions 77 and newer, make sure the Chrome version installed on your machine (including other users) is suitable.
Read more >DevToolsActivePort file doesn't exist - ChromeDriver through ...
The issue still happens on my system: Linux Ubuntu 16, Chrome driver 74. 2019-03-14 10:39:25,305 ERROR [Log] Unexpected exception while setting browser driver: ......
Read more >How to resolve the "DevToolsActivePort file doesn't exist" error ...
Issue: The user is facing the “DevToolsActivePort file doesn't exist” error message with KRE execution on a Linux machine and the project is ......
Read more >Chrome - DevToolsActivePort file doesn't exist - Ask Ubuntu
Error: unknown error : DevToolsActivePort file doesn't exist The process started from chrome location /usr/bin/google-chrome is no longer ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I still have this problem. I can run headless in the terminal not in the docker container. Can you show me your Dockerfile?
This is a work application and the tests are running fine for others. So getting the whole team on board to switch soon is unlikely. Hoping to find a solution of some kind for now.