Calling Quit on the Chrome IWebDriver instance does not kill the spawned chromedriver.exe instance

[lukeis]

Originally reported on Google Code with ID 3378

Calling Quit on the Chrome IWebDriver instance does not kill the spawned chromedriver.exe
instance.

Webdriver 2.16

Reported by apota@vauto.com on 2012-02-15 18:45:21

[lukeis]

Looking at the C# API, I don't see a Stop() method to end the service. All I see is
a Start() method. 

Reported by apota@vauto.com on 2012-02-16 15:27:46

[lukeis]

The service start/stop code was slightly reconfigured in 2.19. Could you try that and
see if it resolves your issue? If not, an example that reproduces your issue would
be most welcome. 

Reported by james.h.evans.jr on 2012-02-16 17:51:17

• Status changed: NeedsClarification

[lukeis]

Is there a C# Webdriver version for 2.19?. I don't see it on this page..
http://seleniumhq.org/download/

Reported by apota@vauto.com on 2012-02-17 19:46:17

[lukeis]

http://code.google.com/p/selenium/downloads/list

Reported by james.h.evans.jr on 2012-02-17 20:18:46

[lukeis]

I have similar issue, i'm using just driver.close() in the remote webdriver via java
API. (version 19 of chromedriver) using 2.21 of standalone server.

14:08:17.876 INFO - Done: /session/1336611907264/element
14:08:18.921 INFO - Executing: [close window] at URL: /session/1336611907264/window)
[0510/140818:ERROR:ipc_channel_win.cc(124)] pipe error: 109
[0510/140818:ERROR:automation_proxy.cc(387)] Channel error in AutomationProxy.
[0510/140818:ERROR:automation_proxy.cc(387)] Channel error in AutomationProxy.
.\test\automation\proxy_launcher.cc(305): error: Value of: browser.get()
  Actual: false
Expected: true
14:08:19.578 INFO - Done: /session/1336611907264/window

Reported by brad.latus on 2012-05-10 04:16:02

[lukeis]

@brad.latus (comment 5) Using driver.close() will explicitly *not* clean up all resources,
including stopping and exiting the chromedriver.exe process. You should be using driver.quit()
to get this expected behavior.

Reported by james.h.evans.jr on 2012-05-10 11:32:15

[lukeis]

I have since changed to driver.quit().

It still leaves sessions open at least on win 2008 enterprise where my tests are currently
running.

They also do not die when selenium server quits it appears.

Reported by brad.latus on 2012-05-10 23:45:47