"unable to discover open pages" and "Chrome Automation Extension has crashed." on Windows 8.1 RTM

[GoogleCodeExporter]

Issue Description:
ChromeDriver will crash as soon as the ChromeDriver constructor is invoked. No 
special setting is been used. The exact same call works just fine in Windows 8.

Steps to reproduce:
The following C# code snippet reproduces the issue:

var chromeOptions = new ChromeOptions();
chromeOptions.AddArgument("--verbose");
ChromeDriverService chromeDriverService = 
ChromeDriverService.CreateDefaultService("C:\\chromedriver");
chromeDriverService.LogPath = "C:\\thelog.log";
ChromeDriver driver = new ChromeDriver(chromeDriverService, chromeOptions);

Expected result: Chrome browser should load successfully.

Actual result: InvalidOperationException: "unknown error: unable to discover 
open pages". Also, this error pops up in the task bar: "Chrome Automation 
Extension has crashed."

OS: Windows 8.1 x64 RTM
Browser: Chrome 29
Chrome Driver: 2.3
WebDriver: 2.35
.Net Framework 4.5

Please see the attached log file.

Original issue reported on code.google.com by JCas...@gmail.com on 24 Sep 2013 at 5:35

Attachments:

• thelog.log

[GoogleCodeExporter]

I experienced the same issue this week. The only difference is that it was 
working on WIN 8.1. Not sure it's caused by a recent chrome update.

Original comment by tnl...@gmail.com on 2 Oct 2013 at 2:29

[GoogleCodeExporter]

I am hitting the same issue, using:
OS: Windows 7 x64
Browser: Chrome 31
Chrome Driver: 2.6
WebDriver: 2.37
.NET 4.5 

Original comment by JohnG...@gmail.com on 18 Nov 2013 at 10:21

[GoogleCodeExporter]

I am also seeing the same issue:
OS: Windows 7 x64
Browser: Chrome 31
Chrome Driver: 2.6, 2.7
WebDriver: 2.37
.NET 4.5

Original comment by zek...@gmail.com on 4 Dec 2013 at 11:09

[GoogleCodeExporter]

It's interesting to note that when I compile with .NET 4.0 I don't see this 
issue, can some one verify? (Not sure if there is in fact a link here)

Original comment by zek...@gmail.com on 4 Dec 2013 at 11:16

[GoogleCodeExporter]

I still have this issue even when compiling against .NET 4.0.

Original comment by JohnG...@gmail.com on 6 Dec 2013 at 9:57

[GoogleCodeExporter]

Seeing same on Win 8.1 

Original comment by amus...@gmail.com on 6 Dec 2013 at 11:34

[GoogleCodeExporter]

A similar issue was found and fixed in chromedriver 2.6. If anyone's still 
seeing this issue on older versions of chromedriver, the first thing to do 
would be to upgrade to the latest release (currently 2.7).

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

If you're seeing this issue on 2.6+, please post the output of the following:

1. run chromedriver with logging turned on
2. open up the log file, and read the port number that is passed to chrome via 
the --remote-debugging-port argument (e.g. JCasaIt's example uses 
--remote-debugging-port=58553)
3. navigate to localhost:58553/json (replace 58553 with whatever port you've 
got)

Original comment by samu...@chromium.org on 9 Dec 2013 at 5:08

[GoogleCodeExporter]

A workaround I found is to use the "--no-sandbox" flag (not optimal but if 
you're desperate).  

PS.  I'm still seeing this issue on with Chomedriver 2.8, but can't get any 
logs because logging is broken (issue 638)
OS: Windows 8.1 x64 RTM
Browser: Chrome 32.0.1700.41 m Aura
Chrome Driver: 2.8
WebDriver: 2.39
.NET 4.5

Original comment by RPW...@gmail.com on 7 Jan 2014 at 2:05

[GoogleCodeExporter]

We are also employing the --no-sandbox flag as a workaround for now.

Original comment by JohnG...@gmail.com on 30 Jan 2014 at 9:22

[GoogleCodeExporter]

@RPWong, chromedriver 2.9 has recently been released, which fixes the logging 
issue on Windows. Could you try using that, and post your logs?

Original comment by samu...@chromium.org on 3 Feb 2014 at 11:50

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I tried going to localhost12614/json but all it has is an empty array:
[  ]

Attached the chromedriver logs

OS: Windows 8.1 x64 RTM
Browser: Chrome 32.0.1700.107 m
Chrome Driver: 2.9
WebDriver: 2.39
.NET 4.5

Original comment by RPW...@gmail.com on 5 Feb 2014 at 12:52

Attachments:

• webdriverLog.txt

[GoogleCodeExporter]

Works for me on both Windows 7 and 8.1.

Do you have any local policies set up such as extension whitelisting (see 
chrome://policy)?

Another thing to try would be to launch chrome directly (rather than through 
chromedriver) and see what comes up at localhost:12614/json. The command line 
is on the second-last line (75) of your webdriverLog.txt file.

Original comment by samu...@chromium.org on 6 Feb 2014 at 10:28

[GoogleCodeExporter]

No local policies from chrome://policy.

I'm able to launch chrome fine through a command line (although I had to modify 
the load extension's path to point to a scoped_dir that existed.)

Original comment by RPW...@gmail.com on 6 Feb 2014 at 11:09

[GoogleCodeExporter]

Did anything come up at localhost:12614/json or was it an empty array again?

Original comment by samu...@chromium.org on 6 Feb 2014 at 11:25

[GoogleCodeExporter]

Oops missed that part of the instructions.  Loading the localhost:12614/json 
does return the following:

[ {
   "description": "",
   "devtoolsFrontendUrl": "/devtools/devtools.html?ws=localhost:12614/devtools/page/B21C3142-8CEE-4952-913D-4972333EAB33",
   "id": "B21C3142-8CEE-4952-913D-4972333EAB33",
   "title": "data:,",
   "type": "page",
   "url": "http://localhost:12614/json",
   "webSocketDebuggerUrl": "ws://localhost:12614/devtools/page/B21C3142-8CEE-4952-913D-4972333EAB33"
}, {
   "description": "",
   "devtoolsFrontendUrl": "/devtools/devtools.html?ws=localhost:12614/devtools/page/BC228C2E-1FC3-41FA-BD7E-1D56B0DA8754",
   "faviconUrl": "chrome://extension-icon/aapnijgdinlhnhlmodcfapnahmbfebeb/24/1",
   "id": "BC228C2E-1FC3-41FA-BD7E-1D56B0DA8754",
   "title": "Chrome Automation Extension",
   "type": "background_page",
   "url": "chrome-extension://aapnijgdinlhnhlmodcfapnahmbfebeb/_generated_background_page.html",
   "webSocketDebuggerUrl": "ws://localhost:12614/devtools/page/BC228C2E-1FC3-41FA-BD7E-1D56B0DA8754"
} ]

Original comment by RPW...@gmail.com on 6 Feb 2014 at 11:49

[GoogleCodeExporter]

@RPWong, the output of localhost:12614/json looks good to me.

Would mind trying with verbose logging and please send us the chromedriver.log?
https://sites.google.com/a/chromium.org/chromedriver/logging

From chromedriver.log with verbose logging turned on, we could know more 
details of what's going on with the chromedriver server and the errors you run 
into.

Besides the error "unable to discover open pages", do you also run into "Chrome 
Automation Extension has crashed."?

Original comment by st...@chromium.org on 7 Feb 2014 at 12:52

• Changed title: "unable to discover open pages" and "Chrome Automation Extension has crashed." on Windows 8.1 RTM

[GoogleCodeExporter]

Attached the verbose log.

Yes I see popups saying the following extensions have crashed:
Feedback
Settings 
Hangout Services
Chrome Automation Extension

Original comment by RPW...@gmail.com on 7 Feb 2014 at 2:42

Attachments:

• chromedriverLogs.log

[GoogleCodeExporter]

Also I noticed that the error now says:
OpenQA.Selenium.WebDriverException: OpenQA.Selenium.WebDriverException: The 
HTTP request to the remote WebDriver server for URL 
http://localhost:53849/session timed out after 60 seconds. ---> 
System.Net.WebException: The operation has timed out. Aborting test execution.

Original comment by RPW...@gmail.com on 7 Feb 2014 at 2:44

[GoogleCodeExporter]

I copied the internal folder that contained the chrome automation extension 
that got created (last time I just picked another internal folder that was 
already laying around the temp folder, which I guess might have been an old 
one?) and tried to run chrome through the command line again.  This time chrome 
started but the chrome automation extension crashed; the other extensions 
(feedback, etc) did not crash.

In the command prompt I see the following errors:
[4624:14460:0206/190904:ERROR:desktop_root_window_host_win.cc(746)] NOT 
IMPLEMENTED
[4624:14460:0206/190904:ERROR:child_process_launcher.cc(332)] Failed to launch 
child process

Original comment by RPW...@gmail.com on 7 Feb 2014 at 3:11

[GoogleCodeExporter]

*edit* (you should add an actual edit button :) )
There was also another error I missed:
[4624:14460:0206/190904:ERROR:chrome_views_delegate.cc(176)] NOT IMPLEMENTED

Original comment by RPW...@gmail.com on 7 Feb 2014 at 3:14

[GoogleCodeExporter]

I am running into this issue with the latest driver (2.9). --no-sandbox works 
fine though - any idea when this might get fixed?

Original comment by chandram...@gmail.com on 2 Apr 2014 at 7:42

[GoogleCodeExporter]

Original comment by samu...@chromium.org on 21 Feb 2015 at 12:18

• Changed state: Unconfirmed

[GoogleCodeExporter]

Tried on both Win 8.1 and Win 7, i am not able to reproduce the issue with 
latest version of chromedriver 2.14

Can you please try with latest version and let us know if you see the issue?

Original comment by gmanikp...@chromium.org on 7 Apr 2015 at 10:16

• Added labels: Needs-Feedback