Issue 8154 in selenium: Unable to load chrome session due to WatchDog timeout issue

[sele...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Status-Untriaged

New issue 8154 by bose.sub...@gmail.com: Unable to load chrome session due
to WatchDog timeout issue
https://code.google.com/p/selenium/issues/detail?id=8154

Selenium script tries to load up a chromedriver session as part of the
script start up and initialization. However the chorme instance just dies
because of watchdog timeout issue.

1. I have tried installing chrome
2. Killing all existing chrome sessions and restarting my computer
3. Downgrade the chrome driver versions

Digging deep into the issue :
Ran the chrome driver and checked the status on localhost:xxxx/status
It takes a considerable amount of time to come back with the status where
as the Watch dog throws the time out exception.


Selenium version: 2.42.2
OS: Windows 7
Browser: Chrome
Browser version: 38.0.2125.122 m


******************************************
Starting ChromeDriver (v2.9.248315) on port 44771
Nov 12, 2014 1:08:45 PM org.openqa.selenium.os.UnixProcess$SeleniumWatchDog
destroyHarder
INFO: Command failed to close cleanly. Destroying forcefully (v2).
org.openqa.selenium.os.UnixProcess$SeleniumWatchDog@3aa6088
Exception in thread "main"
org.openqa.selenium.remote.UnreachableBrowserException: Could not start a
new session. Possible causes are invalid address of the remote server or
browser start-up failure.
Build info: version: '2.41.0', revision: '3192d8a', time: '2014-03-27
17:18:15'
System info: host: 'MyTerminal', ip: '10.54.205.137', os.name: 'Windows 7',
os.arch: 'amd64', os.version: '6.1', java.version: '1.7.0_51'
Driver info: driver.version: ChromeDriver
at
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:589)
at
org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:240)
at
org.openqa.selenium.chrome.ChromeDriver.startSession(ChromeDriver.java:181)
at
org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:126)
at
org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:139)
at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:160)
at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:149)
at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:106)
at ChromeTest.main(ChromeTest.java:16)
Caused by: org.openqa.selenium.WebDriverException: Timed out waiting for
driver server to start.
Build info: version: '2.41.0', revision: '3192d8a', time: '2014-03-27
17:18:15'
System info: host: 'MyTerminal', ip: '10.54.205.137', os.name: 'Windows 7',
os.arch: 'amd64', os.version: '6.1', java.version: '1.7.0_51'
Driver info: driver.version: ChromeDriver
at
org.openqa.selenium.remote.service.DriverService.start(DriverService.java:165)
at
org.openqa.selenium.remote.service.DriverCommandExecutor.execute(DriverCommandExecutor.java:62)
at
org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:568)
... 8 more
Caused by: org.openqa.selenium.net.UrlChecker$TimeoutException: Timed out
waiting for [http://localhost:44771/status] to be available after 20001 ms
at
org.openqa.selenium.net.UrlChecker.waitUntilAvailable(UrlChecker.java:104)
at
org.openqa.selenium.remote.service.DriverService.start(DriverService.java:163)
... 10 more
Caused by: com.google.common.util.concurrent.UncheckedTimeoutException:
java.util.concurrent.TimeoutException
at
com.google.common.util.concurrent.SimpleTimeLimiter.callWithTimeout(SimpleTimeLimiter.java:143)
at
org.openqa.selenium.net.UrlChecker.waitUntilAvailable(UrlChecker.java:79)
... 11 more
Caused by: java.util.concurrent.TimeoutException
at java.util.concurrent.FutureTask.get(FutureTask.java:201)
at
com.google.common.util.concurrent.SimpleTimeLimiter.callWithTimeout(SimpleTimeLimiter.java:130)
... 12 more


******************************************

NOTE : The same scripts were working on the same machine a day before and
today onwards I am getting the error ALWAYS !!

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[sele...@googlecode.com]

Updates:
Status: Invalid

Comment #1 on issue 8154 by barancev: Unable to load chrome session due to

WatchDog timeout issue
https://code.google.com/p/selenium/issues/detail?id=8154

Update chromedriver, the latest version is 2.12

http://chromedriver.storage.googleapis.com/index.html

[sele...@googlecode.com]

Comment #2 on issue 8154 by iamban...@gmail.com: Unable to load chrome

session due to WatchDog timeout issue
https://code.google.com/p/selenium/issues/detail?id=8154

I am using the Chromedriver version 2.15 and still facing the same issue.
Many times Chrome Browser fails to start with same Exception:
INFO: Launching Chrome Browser
Starting ChromeDriver 2.15.322448
(52179c1b310fec1797c81ea9a20326839860b7d3) on port 20537
Only local connections are allowed.

org.openqa.selenium.remote.UnreachableBrowserException: Could not start a
new session. Possible causes are invalid address of the remote server or
browser start-up failure.

Build info: version: 'unknown', revision: 'unknown', time: 'unknown'
System info: host: 'PUNITP89454L', ip: '172.21.41.103', os.name: 'Windows
7', os.arch: 'x86', os.version: '6.1', java.version: '1.8.0_25'

Driver info: driver.version: ChromeDriver
at

org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:593)
at
org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:240)

at
org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:126)
at
org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:139)
at

org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:171)

at
org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:160)
at

org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:117)

[sele...@googlecode.com]

Comment #3 on issue 8154 by it...@spreadshirt.net: Unable to load chrome

session due to WatchDog timeout issue
https://code.google.com/p/selenium/issues/detail?id=8154

Hello,

I am using Chromedriver version 2.16, with Selenium 2.46 and I al also
getting the same error, I have seen it in the log of the grid node.

Is there something I can configure to avoid this situation? Or at least a
known version that is working?

Thanks,

[sele...@googlecode.com]

Comment #4 on issue 8154 by sandhy...@bezelsoft.com: Unable to load chrome

session due to WatchDog timeout issue
https://code.google.com/p/selenium/issues/detail?id=8154

Hi

I am using ChromeDriver 2.16 Selenium 2.47 and am also getting this error
some times .

If it is a chrome driver issue , then why its not showing this error in
every run.

Now, am trying by adding driver.close and then driver.quit() .