Open marvelm opened 3 months ago
@marvelm, thank you for creating this issue. We will troubleshoot it as soon as we can.
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!
Would you like to help us and send a PR?
This issue is looking for contributors.
Please comment below or reach out to us through our IRC/Slack/Matrix channels if you are interested.
I have started to have this issue on my repo about two weeks ago too - https://github.com/ptrdom/scalajs-esbuild/actions/runs/8969102614. Only Windows jobs fail, and it seems to be related to timeouts on quitting the driver. The project with this issue is JVM-based.
Might also be a bug with some recent release of chromedriver v124.
What happened?
Hello,
Apologies for the vague title, but it completely summarizes what we've been experiencing.
When running this code with a profiler, we discovered that
send_remote_shutdown_command
is taking >30 seconds to finish.To get to the bottom of the issue, we monkey-patched this function. This gave us an unexpected output.
.quit()
was only called 3 times, but the output shows thatsend_remote_shutdown_command
was called 6 times. I think it's because__exit__
is being called by thewith
statement. https://github.com/SeleniumHQ/selenium/blob/ba27d0f7675a3d8139544e5522b8f0690a2ba4ce/py/selenium/webdriver/remote/webdriver.py#L216-L222On macOS and Linux, calling
quit()
twice is quick because the default TCP socket timeout is low. However on Windows, the default timeout is long. https://github.com/SeleniumHQ/selenium/blob/ba27d0f7675a3d8139544e5522b8f0690a2ba4ce/py/selenium/webdriver/common/service.py#L126Solution
We're working around this issue on Windows by monkey-patching the function and setting the timeout to a small value.
How can we reproduce the issue?
Relevant log output
Operating System
Windows 10
Selenium version
4.19.0
What are the browser(s) and version(s) where you see this issue?
124.0.6367.60
What are the browser driver(s) and version(s) where you see this issue?
ChromeDriver 123.0.6312.122
Are you using Selenium Grid?
No response