per the Selenium API, you really should call
browser.quit() as this method will close all windows and kills the process. You should still use
However: At my workplace, we've noticed a huge problem when trying to execute chromedriver tests in the Java platform, where the chromedriver.exe actually still exists even after using
browser.quit(). To counter this, we created a batch file similar to this one below, that just forces closed the processes.
@echo off rem just kills stray local chromedriver.exe instances. rem useful if you are trying to clean your project, and your ide is complaining. taskkill /im chromedriver.exe /f
Since chromedriver.exe is not a huge program and does not consume much memory, you shouldn't have to run this every time, but only when it presents a problem. For example when running Project->Clean in Eclipse.
~ Answered on 2014-01-23 22:48:04