Closed frank-calma closed 9 years ago
chromedriver.exe usually gets killed when you do a browser.quit(). Is your browser closing correctly after the test?
Just don't forget to call driver.quit()
Yes, we are calling driver.quit(). The chromedriver instance is being closed from the task manager / process / PID level, but remains as a memory fragment.
Why did you close this issue?
Same problem for with Chrome Standalone, I`m also using driver.quit() properly, I also tried another suggestions that I saw on the web (DBUS_SESSION_BUS_ADDRESS=/dev/null) but this error is still almost 3 years after the last message.
I hate to say it, but my my co-worker and I've been able to replicate this issue even while calling driver.quit. (The second screenshot is after a few moments of the process running.)
We are calling a page request with resque every couple of minutes to verify a page. Yet all processes are still remaining after the closing out the selenium request.
@tarellel Please submit a new issue and include all information specified in the new issue template.... this issue is already closed. Also, "me too" comments with no relevant details are entirely unhelpful.
We run a fairly aggressive distributed selenium grid, executing ~200 tests per node machine per hour. Each test is run using a new chrome driver instance. We have found that the memory on our nodes gradually fills up. After some investigation, we found that our selenium standalone server was holding on to thousands of handles to dead chromedriver instances. Each one was taking up 20kb of ram, and no longer attached to any live process / PID. After resetting the server, these zombie processes were immediately released from memory. At present we have not attempted to replicate the issue using firefox/IE or through local execution.