-
-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WebDriverException: Session was terminated due to TIMEOUT. Grid v2.50.0 #1557
Comments
👍 We've just encountered this as well. Bug from 2.49.0 possibly re-introduced? |
Same happens to me in both Firefox and Chrome. Had to revert to 2.47.1 and Firefox 41 to get my tests to run. |
We've also ran into this issue and had to revert to 2.48.x |
2.50.1 has been released |
@lukeis 👍 Thanks for that! |
going to mark this issue closed/fixed. Feel free to comment if that's not the case and you have steps to reproduce any continued error. |
i have this problem in both 2.52 and 2.53. Using the docker images at https://hub.docker.com/r/selenium/hub/tags/ Error example [2016-09-07 23:20:01] app.CRITICAL: Crawler: WebDriverException failed to fetch url due to message: Session [db903e26-4268-45d9-986c-0aced411ef6f] was terminated due to TIMEOUT I have the problem only when using Firefox apparently $this->driver = RemoteWebDriver::create($host, DesiredCapabilities::firefox(), 3000, 25000); Any clues? is this just a firefox problem? |
We have the same problem with Firefox and Chrome. We are using selenium-java 3.0.0-beta3. Thanks. |
I am having this with 2.53.1, 2.53.0, 2.52.0, 2.51.0. |
I am seeing this with 2.43.1, 2.52.0, 2.51.0 & 2.53.0. |
I am having it in Grid Console v. 3.0.1. |
how i can Avoid this problem ? |
I followed the suggestion in the accepted answer to this question. I never saw the problem again after I did it. I am using selenium 2.53.1: |
I am facing the same issue with Firefox 45 on Linux Rhel 7. At this point I have tried following versions of Selenium 2.47.1 and 2.53.0, on Docker Containers, and they both fail. I have tried several versions of browsers between Firefox 38 and 52. Is there a solution for this?
config.json
|
You can try adding a parameter when starting the node container --shm-size=512m。 |
I upgraded my grid from v2.48.2 to v2.50.0 and now 50% of my tests will get the TIMEOUT error. This is happening on Linux with FF. I have not tried other browsers yet.
I also noticed that if you set the "timeout" option in your node.json file, it gets ignored. Also tried to pass it in through the command line and it was also ignored. This works perfectly fine in v2.48.2.
The text was updated successfully, but these errors were encountered: