[🐛 Bug]: Chrome sessions not being closed properly about selenium HOT 11 CLOSED

Usually this happens when something prevents the driver.quit command from executing. Turn on logging to ensure that the command is getting sent properly.

from selenium.

Yes, the driver should be killing that process when it receives the driver.quit and if that isn't happening for some reason, we need to investigate why. Thanks.

from selenium.

Hello, I had the same pb when upgrading the chromeDriver from 122 to 125 to fit the version to my installed chrome version.
I tried to upgrade too to the latest version 4.21.0 of SeleniumServer, but with no change.
Once we launch one test chrome over consume the CPU. Once the test is fichiched and browser is closed, the process continue to work and consuming CPU and Memory.

It's not a solution but once I did that, it fixed the pb :
I just try to kill process with cmd : taskkill /F /IM chrome.exe /T
And from this moment all is back to normal. So I think that it was an access pb or some think else that I can't understand right now.
I update if I have more information.

from selenium.

I upgraded my platform to the next version 126 ( chromeDirver, and chrome Borwser) And all the pbs are fixed.
thank you

from selenium.

@Harrier-Du-Bois, thank you for creating this issue. We will troubleshoot it as soon as we can.

from selenium.

We need more information about this issue in order to troubleshoot.

Please turn on logging and re-run your code. Information on how to adjust logs for your language can be found in our
Troubleshooting documentation.

from selenium.

Usually this happens when something prevents the driver.quit command from executing. Turn on logging to ensure that the command is getting sent properly.

Thank you for your swift reply.

I also brute forced my way around the issue for now by killing the windows PID at the end of each browser session, similar to @Moez-BenAissa 's workaround.

I'll revert those changes and create a log with the issue happening when I get a chance, maybe tomorrow.

Harrier

from selenium.

We're having the same issue and its more easily reproducible when you are running tests in parallel - we are running over 200 tests where 32 threads are spawned simultaneously but for some reason some chrome instances are not being killed which is hogging the memory and cpu. This is not happening when we run the same set of tests against Firefox.

Also the same issue happens on Edge as both it and Chrome are based off Chromium.

from selenium.

To be clear, this is Chrome and Edge browser processes that are not being closed when the driver is closed?
If the same thing isn't happening with Firefox, than this would indicate that it is a Google bug.

from selenium.

Hi, @Harrier-Du-Bois.
This issue has been determined to require fixes in ChromeDriver.

You can see if the feature is passing in the Web Platform Tests.

If it is something new, please create an issue with the ChromeDriver team.
Feel free to comment the issues that you raise back in this issue. Thank you.

from selenium.

Thank you all for your feedback, great to hear that this issue seems to have been resolved.
Looking forward to my organisation providing me with the working Chrome version.

from selenium.