driver.get hangs chrome version 64 chromedriver 2.35

2,305 views
Skip to first unread message

Matt Strenz

unread,
Jan 26, 2018, 10:09:48 AM1/26/18
to Selenium Users
I am not ever getting a response to be able to continue after using driver.get since updating to chrome version 64.  Updated chromedriver and no change.  
  org.openqa.selenium.TimeoutException: timeout
      (Session info: chrome=64.0.3282.119)
      (Driver info: chromedriver=2.34.522913 (36222509aa6e819815938cbf2709b4849735537c),platform=Linux 4.4.0-111-generic x86_64) (WARNING: The server did not provide any stacktrace information)
    Command duration or timeout: 0 milliseconds
    Build info: version: '3.6.0', revision: '6fbf3ec767', time: '2017-09-27T15:28:36.4Z'
    System info: host: 'aef0474c6132', ip: '172.20.0.3', os.name: 'Linux', os.arch: 'amd64', os.version: '4.4.0-111-generic', java.version: '1.8.0_151'
    Driver info: org.openqa.selenium.chrome.ChromeDriver
    Capabilities [{mobileEmulationEnabled=false, hasTouchScreen=false, platform=LINUX, acceptSslCerts=true, webStorageEnabled=true, browserName=chrome, takesScreenshot=true, javascriptEnabled=true, platformName=LINUX, setWindowRect=true, unexpectedAlertBehaviour=, applicationCacheEnabled=false, rotatable=false, networkConnectionEnabled=false, chrome={chromedriverVersion=2.34.522913 (36222509aa6e819815938cbf2709b4849735537c), userDataDir=/tmp/.org.chromium.Chromium.jUJILA}, takesHeapSnapshot=true, pageLoadStrategy=normal, unhandledPromptBehavior=, databaseEnabled=false, handlesAlerts=true, version=64.0.3282.119, browserConnectionEnabled=false, nativeEvents=true, locationContextEnabled=true, cssSelectorsEnabled=true}]
    Session ID: 68a529a97bbae144f6d8c26efdcc4dc6
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
        at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:214)
        at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:166)
        at org.openqa.selenium.remote.http.JsonHttpResponseCodec.reconstructValue(JsonHttpResponseCodec.java:40)
        at org.openqa.selenium.remote.http.AbstractHttpResponseCodec.decode(AbstractHttpResponseCodec.java:82)
        at org.openqa.selenium.remote.http.AbstractHttpResponseCodec.decode(AbstractHttpResponseCodec.java:45)
        at org.openqa.selenium.remote.HttpCommandExecutor.execute(HttpCommandExecutor.java:164)
        at org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:83)
        at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:586)
        at org.openqa.selenium.remote.RemoteWebDriver.get(RemoteWebDriver.java:310)

Is anybody else experiencing this?  Started yesterday afternoon.

brandon....@gesture.com

unread,
Jan 26, 2018, 2:57:20 PM1/26/18
to Selenium Users
I am having the same problem and have been actively trying to figure it out since they released v 64.0.3282 (Wednesday).

Aleksandr Melnikov

unread,
Jan 26, 2018, 2:57:20 PM1/26/18
to Selenium Users
What version of Selenium are you using? 3.6.0?

brandon....@gesture.com

unread,
Jan 26, 2018, 2:59:46 PM1/26/18
to Selenium Users
I have verified that this is occurring with Selenium 2.41, 2.53, and 3.8.1. I'm using Chrome 64.0.3282 and ChromeDriver 2.35.

brandon....@gesture.com

unread,
Jan 26, 2018, 4:03:36 PM1/26/18
to Selenium Users
I made a little progress, but it's not good news. When performing any method belonging to the WebDriver class, the driver randomly becomes unresponsive. This could be a driver.get(), driver.manage().addCookie(), driver.manage().logs(), etc. All of the following have happened to me today.

Aleksandr Melnikov

unread,
Jan 28, 2018, 1:05:54 PM1/28/18
to seleniu...@googlegroups.com
Sounds frustrating. Are you using headless mode? 

--
You received this message because you are subscribed to the Google Groups "Selenium Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to selenium-users+unsubscribe@googlegroups.com.
To post to this group, send email to selenium-users@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-users/807a7c5c-ae45-4125-9cf8-272ce3c714de%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Matt Strenz

unread,
Jan 29, 2018, 10:07:54 AM1/29/18
to Selenium Users
No on headless.  Chromedriver version 2.35.  Hangs inside the execute
To unsubscribe from this group and stop receiving emails from it, send an email to selenium-user...@googlegroups.com.
To post to this group, send email to seleniu...@googlegroups.com.

Aleksandr Melnikov

unread,
Jan 29, 2018, 12:30:23 PM1/29/18
to seleniu...@googlegroups.com
I'm having separate issues myself, I can't seem to get the window handles to work properly with xfvb.

But to maybe help you, have you checked your inode and disk space?
"df -h" for disk space, "df -i" for inode.

I've had an issue before related to that, and at this point, I would check all sorts of stuff to figure out what might be causing this.

-Aleksandr Melnikov

To unsubscribe from this group and stop receiving emails from it, send an email to selenium-users+unsubscribe@googlegroups.com.
To post to this group, send email to selenium-users@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/selenium-users/b6119933-1d2c-4496-8c8e-2c3436bd64ec%40googlegroups.com.

magdale...@motorolasolutions.com

unread,
Jan 31, 2018, 8:04:22 AM1/31/18
to Selenium Users
I'm having the same issue using Saucelabs (chrome 64, webdriver 2.34) - not observed for chrome 63

Максим Деменко

unread,
Jan 31, 2018, 10:01:16 AM1/31/18
to Selenium Users
Same for me:   (Session info: chrome=64.0.3282.119)
  (Driver info: chromedriver=2.35.528161 (5b82f2d2aae0ca24b877009200ced9065a772e73),platform=Windows NT 6.1.7601 SP1 x86_64) (WARNING: The server did not provide any stacktrace information)

среда, 31 января 2018 г., 15:04:22 UTC+2 пользователь magdale...@motorolasolutions.com написал:

brandon....@gesture.com

unread,
Jan 31, 2018, 10:15:30 AM1/31/18
to Selenium Users
I opened a bug ticket with Chromium... it would be great if you would comment there to push them a bit harder to find a fix. Here's the link:

Rajeev JordaN

unread,
Feb 13, 2018, 2:13:09 AM2/13/18
to Selenium Users
Even I am unable to use, please let me know if someone got the solution already

Rajeev JordaN

unread,
Feb 13, 2018, 2:13:22 AM2/13/18
to Selenium Users
I have Chrome (chrome=64.0.3282.140) Please let me know how to get V63, as I tried installing it from a dmg but it gets updated automatically

Loren Guthrie

unread,
Feb 17, 2018, 8:59:02 AM2/17/18
to Selenium Users
I am seeing this timeouts as well:
    (Session info: chrome=64.0.3282.167)
    (Driver info: chromedriver=2.35.528157 (4429ca2590d6988c0745c24c8858745aaaec01ef),platform=Mac OS X 10.12.6 x86_64)


On Friday, January 26, 2018 at 7:09:48 AM UTC-8, Matt Strenz wrote:

vtlrbcc

unread,
Feb 23, 2018, 11:06:29 PM2/23/18
to Selenium Users
I'm getting this, too.  Anyone found a fix?

TimeoutException: Message: timeout

Marek Balicki

unread,
Feb 26, 2018, 12:02:16 PM2/26/18
to Selenium Users
Yes. Downgrade ChromeDriver to 2.33. 

antonku...@gmail.com

unread,
Apr 26, 2018, 12:48:13 AM4/26/18
to Selenium Users
Same happening for me constantly,

Opened new defect:

Jonathan Herbaut

unread,
Apr 26, 2018, 9:50:38 AM4/26/18
to Selenium Users
Currently using Chrome 66 Headless on Ubuntu and Chrome 66 (normal) on Windows with WebDriver 2.37 through Grid 3.11.0 and don't get any problem.
Reply all
Reply to author
Forward
0 new messages