-
-
Notifications
You must be signed in to change notification settings - Fork 8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
High CPU usage with chromedriver 124.0.6367.78 and selenium-java 4.20.0[馃悰 Bug]: #13872
Comments
@dmidura, thank you for creating this issue. We will troubleshoot it as soon as we can. Info for maintainersTriage this issue by using labels.
If information is missing, add a helpful comment and then
If the issue is a question, add the
If the issue is valid but there is no time to troubleshoot it, consider adding the
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable
After troubleshooting the issue, please add the Thank you! |
I've had the exact same problem since yesterday |
Yes, this has been reported. Unfortunately, we cannot fix this issue as it is in Chrome. |
I have been facing this issue since last week .. This is not only about Chrome 124 it is also Happening with firefox and edge browser . |
Same issue i'm facing too.. first iteration starts fine and after the browser closes and restart then issue is back |
Added a comment in the chrome driver bugs link https://bugs.chromium.org/p/chromedriver/issues/detail?id=4744 "The issue still exists with chromedriver version 124.0.6367.155 and chrome browser version 124.0.6367.119. As the original author recommended below 2 options
Nothing works for us. Attached is the screenshot which shows when a simple testcase to open chrome launch google.com and close it is run 10 times and the processes still exists even after testcases are completed and browsers are closed by chrome driver. Note: during execution, if I manually close the browser, no more zombie processes left." |
You need to call |
I was having the same problem. As a possible work around you could comment out or remove chromeOpts.addArguments("--no-sandbox"); in your driver initialization. For me it reduced the CPU load. |
This issue has been automatically locked since there has not been any recent activity since it was closed. Please open a new issue for related bugs. |
What happened?
I am seeing very high CPU usage when running automation. The Chrome processes are not quitting after the automation directs the driver to quit. Instead, they collect in the background and just add to the CPU load. This just started when chrome upgraded to 124.0.6367.79. I was running selenium-java 4.19.1, but I've tried with 4.20.0 and haven't seen an improvement.
I am on chromedriver 124.0.6367.79
I am using selenium-java 4.20.0
I am running in a Windows environment.
Can someone please tell me how to reduce the CPU load clocking for my automation?
How can we reproduce the issue?
Relevant log output
I can only see this is happening by looking at the running processes in my windows task manager.
Operating System
Windows 11 Enterprise
Selenium version
4.19.1, 4.20.0
What are the browser(s) and version(s) where you see this issue?
Chrome 124.0.6367.79
What are the browser driver(s) and version(s) where you see this issue?
chromedriver 124.0.6367.78
Are you using Selenium Grid?
no
The text was updated successfully, but these errors were encountered: