chromedriver_2.33.exe hangs around after test finishes.

[delfu]

Bug 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

[acuper]

I had the same issue, downgrade of server helped:
webdriver-manager update --versions.standalone 3.4.0

[delfu]

yep that seems to have fixed it. @cnishina you mentioned a fix in a stackoverflow answer This seems to have been broken from 3.4.0 to latest (3.7.0)

[ezekeal]

This issue can be reporoduced with the config file and spec files here on Windows 10
it uses both
directConnect
and
restartBrowserBetweenTests
spec and config on pastebin

[wswebcreation]

Is this issue still valid with the latest version of chromedriver?

[vsravuri]

I see this issue with Chromedriver 2.34

[ezekeal]

Our issue was resolved by removing the flag --no-sandbox from our test config.

[sisbilir]

I still see the issue with Chromedriver 2.35

[sisbilir]

I don't have this issue with 2.37.

[delfu]

Still an issue in 2.39