High CPU usage with chromedriver 124.0.6367.78 and selenium-java 4.20.0[🐛 Bug]:

[dmidura]

High CPU usage with chromedriver 124.0.6367.78 and selenium-java 4.20.0[🐛 Bug]:

[Rodaxfck]

I've had the exact same problem since yesterday
Multiple running chrome processes and remaining "chromedriver.exe" after some test executions
My laptop was slower and slower and I noticed this
https://bugs.chromium.org/p/chromedriver/issues/detail?id=4744

[balivadas]

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.
After testcase is run, and completed (chrome driver is quit), the Google Chrome process still exists with 2 threads running consuming on an average 10% of CPU utilization.
If i run 10 testcases, it means 100% CPU utilization and this is making the system very slow.

As the original author recommended below 2 options
IMPORTANT TIPS:

1. This is related to "--no-sandbox" browser argument. As soon as I remove this argument, I don't see "zombie processes".
2. If I really want to use "--no-sandbox" argument, and I add "--remote-debugging-pipe", then the issue is not reproducible anymore - no "zombie" processes.

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."

[GerbenArkesteijn]

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.

[github-actions]

@dmidura, thank you for creating this issue. We will troubleshoot it as soon as we can.

---

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

[diemol]

Yes, this has been reported. Unfortunately, we cannot fix this issue as it is in Chrome.

[DeepakSahu-Engineer]

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 .

[vinoth959]

Same issue i'm facing too.. first iteration starts fine and after the browser closes and restart then issue is back

[RileyXX]

You need to call driver.close() before driver.quit() otherwise you get lingering chrome processes with high resource usage. This is an issue with recent chrome versions (124+).