chromedriver_2.33.exe hangs around after test finishes.
See original GitHub issueBug report
when running webdriver-manager update
and protractor config.js
the test processes properly, but upon finishing, leaves behind a chrome_2.33.exe and never cleans it up.
-
Node Version:
8.7.0
-
Protractor Version:
5.2.0
-
Angular Version:
1.5.8
-
Browser(s):
chrome 62
-
Operating System and Version
Windows 10
-
protractor configuration file: very simple, no other settings other than listed
framework: "jasmine", plugins: [], jasmineNodeOpts: { defaultTimeoutInterval: 120000 }, capabilities: { "browserName": "chrome", "chromeOptions": { "args": ["--window-size=1200,1000"] } }, suites: { example: "spec.js" }
this causes a new chromedriver.exe to pile up after each time we test. and makes it impossible for us to do a clean build without having to kill all the processes beforehand
Issue Analytics
- State:
- Created 6 years ago
- Comments:9 (1 by maintainers)
Top Results From Across the Web
Chrome driver process does not auto-close (hangs around ...
It seems that by providing the directConnect: true parameter in the conf.ts for Protractor, the chromedriver.exe will be closed after the test ...
Read more >chromedriver.exe hangs when running multiple test cases
chromedriver.exe stopped working. The HTTP request to the remote WebDriver server for URL session timed out after 60 seconds. Specification.
Read more >2311 - Chromedriver leaves forked Chrome instances ...
The chromedriver.exe stops 4-5 secs after the tests completed. Then the forked Chrome instances stay in the background as running processes with huge...
Read more >ChromeDriver randomly "freezes" for 70-90 seconds, causing ...
Test -side (C#) driver class times out after 60 seconds of ChromeDriver inactivity and fails the test. These "freezes" occur at random times,...
Read more >Downloads - ChromeDriver - WebDriver for Chrome
ChromeDriver 84.0.4147.30. Supports Chrome version 84. Resolved issue 3420: after switching to the print window, the chromedriver stops responding ...
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
Still an issue in 2.39
I had the same issue, downgrade of server helped: webdriver-manager update --versions.standalone 3.4.0