Closed cybertuck closed 1 month ago
@cybertuck, 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!
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.
This is likely a chromedriver issue, but it'll be easier to tell with better logs
Sounds like this issue to me: https://bugs.chromium.org/p/chromedriver/issues/detail?id=4596
@titusfortner Usually the users try to call driver.quit after a exception, so we could check the health of the driver process before executing the command (or all commands?) and raise a DriverTerminatedUnexpectedException
to signal this is most likely not a selenium issue?
PS: i had a short look at the code and there is some kind of logic to handle this, here: https://github.com/SeleniumHQ/selenium/blob/1b827c2b297988d4856bcee666f7b593fc8dc526/java/src/org/openqa/selenium/remote/service/DriverCommandExecutor.java#L121
But this code makes no sense to me, the process alive check does return a null response, this could explain the empty WebDriverException in the reported issue.
I will have a look at this in some days and at least fix the current implementation.
@joerg1985 You are right. My issue is similar to yours https://bugs.chromium.org/p/chromedriver/issues/detail?id=4596 When I run via Selenoid I`m getting "Command duration or timeout: 469 milliseconds" exception. I also was able to reproduce it locally with standalone selenium server and the exception is "ConnectException: Connection refused: no further information" @titusfortner If you want to reproduce joerg provided a test example in #4596 bugs.chromium
Hi, @cybertuck. 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.
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?
Worked fine with ChromeDriver 105.0 Problem appears when I switched to the latest version 125.0
How can we reproduce the issue?
Relevant log output
Operating System
RHEL8
Selenium version
Java 4.18.0
What are the browser(s) and version(s) where you see this issue?
Chrome 123.0, 125.0.6422.142 (Official Build) (32-bit)
What are the browser driver(s) and version(s) where you see this issue?
ChromeDriver 125
Are you using Selenium Grid?
Selenoid