Closed jramirezmorales closed 10 months ago
@jramirezmorales, 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!
I'm just doing a simple explicit wait , not sure if this is causing the thread lock:
wait.until(ExpectedConditions.visibilityOfElementLocated( By.xpath("//market-blade[@class='market-blade']")));
Also I was thinking that the problem was because of a single new WebDriverWait(webDriver, Duration.ofSeconds(30)); object for all waits, so I created new object for every wait.until, but the problem continues
@jramirezmorales
I can't see a dead lock here, the main
thread is waiting for the next round of polling.
A timeout exception should be raised after a while, depending on the timeout of the wait
object.
Could you provide code to reproduce this?
@joerg1985 this is the timeout you mentioned , seems that the timeout may be causing the browser to crash thread dump.txt
@joerg1985 here is another thread dump running same tests, so if the problem are timeouts, which another setting could I use for timeout, apart from
driver.manage().timeouts().scriptTimeout(Duration.ofSeconds(60));
and
new WebDriverWait(webDriver, Duration.ofSeconds(60));
another thread dump.txt
also see this issue just one time
@jramirezmorales Could you provide code to reproduce this? Without the code it is not possible to debug this.
@joerg1985 let me try to wok on a test code to provide it since the code where this issue arise is private
Fluent wait is not working as expected post chrome version 114. I am using Chrome Version 117 and this piece of code stopped working as expected. WebElement myelementowaitfor = (new WebDriverWait(driver,Duration.ofSeconds(10))).until(ExpectedConditions.presenceOfElementLocated(By.name("frameMenu")));
previosly this was - WebElement myelementowaitfor = (new WebDriverWait(driver,10)).until(ExpectedConditions.presenceOfElementLocated(By.name("frameMenu")));
@msharma2020 how is this related to this issue?
@jramirezmorales did you find a way to reproduce this? Otherwise the issue will stale and be closed.
@diemol not so far, have a lot of work to do, not having chance to work on this, I just Ignored all my tests using selenium4 for now :(
I will close this as we did not get more information from the OP. We can reopen it in case more information is provided.
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
What happened?
deadlock in FluentWait(explicitwait)
How can we reproduce the issue?
Relevant log output
Operating System
macOS ventura 13.5
Selenium version
java17
What are the browser(s) and version(s) where you see this issue?
Chrome 116
What are the browser driver(s) and version(s) where you see this issue?
ChromeDriver 116.0.5845.96
Are you using Selenium Grid?
No response