[🐛 Bug]: driver.quit doesn't kill all Chrome processes

[nikitakovaliov92]

[🐛 Bug]: driver.quit doesn't kill all Chrome processes

[ashustovsky]

Works for me (Win 11, Chrome 124.0.6367.92, Driver: 124.0.6367.91)

1. Added argument: "disable-renderer-backgrounding"
2. Make this: Driver.Close(); Driver.Quit(); Driver.Dispose();

[nikitakovaliov92]

@diemol from javadoc

Close the browser if it's open.
NB! Method quits this driver, closing every associated window.
See Also:
WebDriver. quit()

[nikitakovaliov92]

created issue for chrome team: https://issues.chromium.org/issues/336164423

@asolntsev i'm not sure about this comment because another users have the same issue as me on the Chrome 124+......

Just for the record, I cannot reproduce this problem in MacOS. Both Chrome 123 and 124 work well.

[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+).

[github-actions]

@nikitakovaliov92, 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!

[github-actions]

Hi, @nikitakovaliov92.
Please follow the issue template, we need more information to reproduce the issue.

Either a complete code snippet and URL/HTML (if more than one file is needed, provide a GitHub repo and instructions to run the code), the specific versions used, or a more detailed description to help us understand the issue.

Note: If you cannot share your code and URL/HTML, any complete code snippet and URL/HTML that reproduces the issue is good enough.

Reply to this issue when all information is provided, thank you.

[nikitakovaliov92]

selenium.zip
Run tests from attached project several times and look at the task manager Processes tab. There are a lot of Google Chrome items

[diemol]

@asolntsev, what does Selenide.closeWebDriver(); do?

[diemol]

Does this happen in any machine?
I am trying to understand better because if this was an issue, I can imagine many more people reporting it.

[nikitakovaliov92]

Does this happen in any machine? I am trying to understand better because if this was an issue, I can imagine many more people reporting it.

in my case it reproduces on Windows

I can imagine many more people reporting it.

chrome 124 was released 4/16 so maybe not a lot of users have updated it yet

[diemol]

What happens if you try with Chrome 123? Or Chrome for Testing?

[nikitakovaliov92]

Chrome 123 works good

[vibes121]

I am facing same issue with v123 .

[asolntsev]

Just for the record, I cannot reproduce this problem in MacOS. Both Chrome 123 and 124 work well.

[diemol]

@nikitakovaliov92, could you please report this to the Chrome folks?

[github-actions]

Hi, @nikitakovaliov92.
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.

[titusfortner]

According to the Chrome bug report, seems like only an issue when using '--no-sandbox?
Hopefully they fix this because you really shouldn't need to call both close() and quit() (and actually doing so should result in an error)

[Chihitempclaims]

Can you tell me which window version you are using?? i am using Windows 11 Pro edition and working fine in both single instances and multiple instances.
As i am using these chrome options:
op.add_argument('--disable-dev-shm-usage')
op.add_argument("--disable-extensions")
op.add_argument('--disable-gpu')
op.add_argument('--no-sandbox')
# op.add_argument('--headless')
op.add_argument('--start-maximized')
op.add_argument('--window-size=1920x1080')

[Chihitempclaims]

**Can you tell me which window version you are using?? i am using Windows 11 Pro edition and working fine in both single instances and multiple instances(multiprocessing). I didnt encounter any chrome background processes.
As i am using these chrome options:
op.add_argument('--disable-dev-shm-usage')
op.add_argument("--disable-extensions")
op.add_argument('--disable-gpu')
op.add_argument('--no-sandbox')
op.add_argument('--start-maximized')
op.add_argument('--window-size=1920x1080')

[titusfortner]

You shouldn't need most of those arguments unless you are also running headless, and even then you probably don't want --no-sandbox. Please read - https://github.com/GoogleChrome/chrome-launcher/blob/main/docs/chrome-flags-for-tools.md

[Chihitempclaims]

According to the Chrome bug report, seems like only an issue when using '--no-sandbox? Hopefully they fix this because you really shouldn't need to call both close() and quit() (and actually doing so should result in an error)

in 124+ its working fine but as I remember for the previous versions it results in an error. I mostly encounter multiple chrome's background process in mostly VM's with (Windows 10 Enterprise). In linux systems it is working fine.

[ENY66]

I've been having this problem on Windows 10 with v125. The solution described by others here to call driver.close() before driver.quit() improved the situation, but did not solve it completely. Instead, removing chrome_options.add_argument("--no-sandbox") seems to have solved it.