search

FuckTheWorld / chromedriver

Automatically exported from code.google.com/p/chromedriver
0 stars 0 forks source link

ChromeDriver 2.11 not working with Chrome 38 in Windows Server 2008R2 #928

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
See http://goo.gl/ll2FvQ for common issues.

Issue Description:
ChromeDriver can not communicate with Chrome in Windows Server 2008R2

Environment Details
- Windows Server 2008 R2 SP1 (x64)
- Chrome (38.0.2125.101 m)

Steps to reproduce:
1. Execute simple Selenium test against Chrome (example below)

Example test:
IWebDriver _driver = new ChromeDriver();
_driver.Manage().Window.Maximize();

Error details:

Stacktrace

MESSAGE:
Initialization method WebAppTests.HomePageTests.Initialize threw exception. 
OpenQA.Selenium.WebDriverException: OpenQA.Selenium.WebDriverException: The 
HTTP request to the remote WebDriver server for URL 
http://localhost:3581/session/446827e125ab6df59b48ebfde1a33a9a/window/current/ma
ximize timed out after 60 seconds. ---> System.Net.WebException: The operation 
has timed out.
+++++++++++++++++++
STACK TRACE:
    at System.Net.HttpWebRequest.GetResponse()
   at OpenQA.Selenium.Remote.HttpCommandExecutor.CreateResponse(WebRequest request)
 --- End of inner exception stack trace ---
    at OpenQA.Selenium.Remote.HttpCommandExecutor.CreateResponse(WebRequest request)
   at OpenQA.Selenium.Remote.HttpCommandExecutor.Execute(Command commandToExecute)
   at OpenQA.Selenium.Remote.DriverServiceCommandExecutor.Execute(Command commandToExecute)
   at OpenQA.Selenium.Remote.RemoteWebDriver.Execute(String driverCommandToExecute, Dictionary`2 parameters)
   at OpenQA.Selenium.Remote.RemoteWindow.Maximize()
   at Datahug.AutomationFramework.GUI.CommonUtilities.Browser.Initialize() in c:\buildworkspaces\WebApp-FunctionalTests-Build\Datahug.AutomationFramework.GUI\CommonUtilities\Browser.cs:line 59

Other details:

- All other actions timeout as well (is not an isolated issue with .Maximize())
- It works correctly in Windows 7 SP1
- Issue seen after upgrading Chrome to v38 in the Windows Server machine

Original issue reported on code.google.com by victor.p...@datahug.com on 9 Oct 2014 at 9:55

GoogleCodeExporter commented 9 years ago 
The latest ChromeDriver also can not communicate with Chrome 38 on Windows7 
when I run tests with Jenkins. 
Chrome browser simply hangs and it is impossible to get any url. 

selenium logs stop after record:
[1.893][DEBUG]: DEVTOOLS COMMAND Page.enable (id=5) {}

can't reach the next expected step:
[1.924][DEBUG]: DEVTOOLS RESPONSE Console.enable (id=1) {}

Error message:
WebDriverException: Message: u'disconnected: Unable to receive message from 
renderer\n  (Session info: chrome=38.0.2125.101)\n  (Driver info: 
chromedriver=2.11.298604 
(75ea2fdb5c87f133a8e1b8da16f6091fb7d5321e),platform=Windows NT 6.1 SP1 x86_64)'

Original comment by a...@zeoalliance.com on 13 Oct 2014 at 11:47

GoogleCodeExporter commented 9 years ago 
I have to say that I'm also getting the issue on Windows Server 2008 R2 when 
running the tests from Jenkins. So it's probably not a OS issue, is something 
related with Jenkins.

Original comment by victor.p...@datahug.com on 13 Oct 2014 at 12:49

GoogleCodeExporter commented 9 years ago 
We got the same issue for browser tests run with ChromeDriver 2.10 and 2.11 
interacting with Chrome 38 on Windows 7 and 8 though TeamCity.

It runs fine when we logon the build agents and execute the tests manually, but 
nothing happens when they are started by TeamCity.

- Regin

Original comment by regin.la...@eksponent.com on 13 Oct 2014 at 1:32

GoogleCodeExporter commented 9 years ago 
We're also experiencing this problem with running our selenium tests via 
TeamCity.

Original comment by cr...@thequillens.com on 13 Oct 2014 at 4:36

GoogleCodeExporter commented 9 years ago 
We are experiencing this problem on a Windows Server 2012 using jenkins. We 
have the same setting on a cloned machine where the Chrome version is 37 and it 
runs without hassle.

Original comment by heiko.fe...@googlemail.com on 14 Oct 2014 at 7:08

GoogleCodeExporter commented 9 years ago 
We've got these same problems with Chrome 38 on Windows Server 2012R2

10:37:03.366 WARN - Exception thrown
org.openqa.selenium.WebDriverException: unknown error: cannot get automation 
extension
from timeout: Timed out receiving message from renderer: 600.000
  (Session info: chrome=38.0.2125.101)
  (Driver info: chromedriver=2.11.298604 (75ea2fdb5c87f133a8e1b8da16f6091fb7d5321e),platform=Windows NT 6.3 x86_64)

Original comment by overe...@gmail.com on 14 Oct 2014 at 7:12

GoogleCodeExporter commented 9 years ago 
No luck with the beta or dev channel either.

Original comment by regin.la...@eksponent.com on 14 Oct 2014 at 12:07

GoogleCodeExporter commented 9 years ago 
We are experiencing the same problem. 

Issue Description:
We are using combination of chromedriver/webdriverbackedselenium/teamcity for 
our function tests. Since the new release of chrome browser, our tests won't 
start. We tried updating chromedriver to 2.11, webdriver backed selenium to 
2.43.1 but no luck. When we reverted back to chrome browser v37, it works. 
Could you please help? 

Exception we received in teamcity:
OpenQA.Selenium.WebDriverException : The HTTP request to the remote WebDriver 
server for URL 
http://localhost:61387/session/63f6382beec9938da3dc1ef2c2104f74/cookie timed 
out after 60 seconds.

Following if the chrome_debug.log 
[1884:2368:1014/172810:ERROR:gpu_process_transport_factory.cc(418)] Failed to 
establish GPU channel.
[1884:2368:1014/172810:ERROR:child_process_launcher.cc(344)] Failed to launch 
child process
[1884:2368:1014/172810:ERROR:child_process_launcher.cc(344)] Failed to launch 
child process

Steps to reproduce (if relevant, you MUST provide a simplified html page or
link to public site):
Code to initialize chrome options:
var options = new ChromeOptions();
options.AddArgument("--no-experiments");
options.AddArgument("--disable-translate");
options.AddArgument("--disable-plugins");
options.AddArgument("--disable-extensions");
options.AddArgument("--no-default-browser-check");
options.AddArgument("--clear-token-service");
options.AddArgument("--disable-default-apps");
options.AddArgument("--enable-logging");
options.AddArgument("test-type");

var driver = new ChromeDriver(options);
driver.Manage().Timeouts()
.ImplicitlyWait(60)
.SetScriptTimeout(60));

Original comment by puniebal...@gmail.com on 15 Oct 2014 at 6:28

GoogleCodeExporter commented 9 years ago 
We are experiencing the same issue when we run the tests on Jenkins. Tests seem 
to run fine for me locally(and on the build agent if I run the tests manually 
from a command line instead of allowing Jenkins to launch the job).

Have confirmed it's only Chrome 38 giving us the issue, and also that 2.11 
chromedriver doesn't solve this for us(the message below is for chromedriver 
2.9 before we tested 2.11).

18:59:39 TimeoutException: Message: u'timeout: Timed out receiving message from 
renderer: 600.000\n  (Session info: chrome=38.0.2125.101)\n  (Driver info: 
chromedriver=2.9.248315,platform=Windows NT 6.1 SP1 x86_64)' 

Windows 7 slaves.

Original comment by jake.ben...@bromium.com on 15 Oct 2014 at 10:23

GoogleCodeExporter commented 9 years ago 
We are experiencing the same issue on TeamCity a Chrome on Windows Server 2012R2
Chrome: Version 38.0.2125.104 m
Driver 2.11

Original comment by johny200...@gmail.com on 16 Oct 2014 at 8:15

GoogleCodeExporter commented 9 years ago 
In order to promote this issue I've wrote the following blog post:

http://testingisland.wordpress.com/2014/10/16/latest-chrome-not-keen-to-listen-o
ur-selenium-tests-in-jenkins-server/

Please share!

Original comment by victor.p...@datahug.com on 16 Oct 2014 at 9:54

GoogleCodeExporter commented 9 years ago 
Selenium 2.43.1
ChromeDriver 2.11
Chrome 38.0.2125.104
Windows Server 2012 R2

The same issue.

Original comment by Artem.Re...@gmail.com on 16 Oct 2014 at 10:54

GoogleCodeExporter commented 9 years ago 
same issue with jenkins execution => timeout problems
works fine in command line without jenkins

selenium : 2.43.1
chromedriver : 2.11
chrome : 38.0.2125.104 m
jenkins : 1.574
os : windows  server 2008 R2

chromedriver launched corretly
child process chrome launched
other child  chrome process not launched

if it can help :
chromedriver comand line
C:\chromedriver\2.11\chromedriver.exe --port=34091 
--log-path=c:\.jenkins\jobs\AR_VA_NR_Canvas_Tests\wrk\Tests\SeleniumTestLauncher
\target\chromeDriver.log

child process chrome command line
"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" 
--disable-background-networking --disable-client-side-phishing-detection 
--disable-component-update --disable-default-apps --disable-hang-monitor 
--disable-prompt-on-repost --disable-sync --disable-web-resources 
--enable-logging --ignore-certificate-errors 
--load-extension="C:\Users\UserName\AppData\Local\Temp\2\scoped_dir8756_32305\in
ternal" --logging-level=1 --metrics-recording-only --no-first-run 
--password-store=basic --remote-debugging-port=12443 
--safebrowsing-disable-auto-update --safebrowsing-disable-download-protection 
--use-mock-keychain 
--user-data-dir="C:\Users\UserName\AppData\Local\Temp\2\scoped_dir8756_9605" 
data:,

Original comment by tomateet...@gmail.com on 16 Oct 2014 at 5:15

GoogleCodeExporter commented 9 years ago 
We are also experiencing the same problem with teamcity and chromedriver.  
Please update as soon as possible.

Original comment by bret.she...@gmail.com on 16 Oct 2014 at 9:30

GoogleCodeExporter commented 9 years ago 
Hi all, please vote to escalate this issue.

Original comment by puniebal...@gmail.com on 16 Oct 2014 at 11:45

GoogleCodeExporter commented 9 years ago 
Exactly the same environment and issues as described in the first post.

Original comment by augustyn...@gmail.com on 17 Oct 2014 at 10:57

GoogleCodeExporter commented 9 years ago 
Same issue with TeamCity and ChromeDriver

Original comment by yngve.ni...@gmail.com on 17 Oct 2014 at 10:59

GoogleCodeExporter commented 9 years ago 
TeamCity with Chrome 38 and Driver 2.11 same issues. Runs fine from command 
line.

Original comment by richard....@swinton.co.uk on 17 Oct 2014 at 11:15

GoogleCodeExporter commented 9 years ago 
This looks to be a duplicate: 
https://code.google.com/p/chromedriver/issues/detail?id=935

Original comment by yngve.ni...@gmail.com on 17 Oct 2014 at 11:16

GoogleCodeExporter commented 9 years ago 
Hi - For all the others that are facing the same issue with chrome driver 2.11 
and chrome 38 , is there a way to downgrade google chrome to 37 to get this 
going ?
Appreciate the help

Original comment by mehul.ch...@gmail.com on 17 Oct 2014 at 6:10

GoogleCodeExporter commented 9 years ago 
There are standalone chrome installers but they are difficult to find on the 
web.  The best I could find today was a version 35 standalone installer.  Using 
that, disabling google update (this is well documented on the web) and using an 
older version of chromedriver (2.9) I was able to get our tests running on 
TeamCity again.  This is not ideal, but hopefully this is only necessary for a 
brief period of time.

Original comment by w.wils...@gmail.com on 17 Oct 2014 at 9:01

GoogleCodeExporter commented 9 years ago 
The problem seems to be related to "running as service".
When I log-in to the build agent and run the test "manually" then it runs ok, 
but if I run the same command from a windows-service it will fail with:

OpenQA.Selenium.WebDriverException: The HTTP request to the remote WebDriver 
server for URL window/current/maximize timed out after 60 seconds

Original comment by abu...@gmail.com on 19 Oct 2014 at 10:32

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
I agree with @abu above. I run it manually on the slave and it works perfectly 
but it does not work with when run through Jenkins.

Original comment by ast...@zoosk.com on 20 Oct 2014 at 3:25

GoogleCodeExporter commented 9 years ago 
Same problem here.  Runs manually but not through jenkins.

Original comment by andr...@gmail.com on 20 Oct 2014 at 4:41

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
The same. Problem only with running via service.

Original comment by Artem.Re...@gmail.com on 20 Oct 2014 at 6:22

GoogleCodeExporter commented 9 years ago 
We are also getting this problem with TeamCity and ChromeDriver (after Chrome 
auto-updated to 38).

Original comment by ja...@thebatesons.com on 20 Oct 2014 at 9:07

GoogleCodeExporter commented 9 years ago 
We are also getting this issue.

Original comment by james.cr...@gmail.com on 20 Oct 2014 at 11:32

GoogleCodeExporter commented 9 years ago 
I have the exact same issue on Windows Server 2012 nad Windows 7.

Original comment by erlend.r...@gmail.com on 20 Oct 2014 at 11:35

GoogleCodeExporter commented 9 years ago 
We are also seeing the same issue, running a Jenkins slave on Windows Server 
2008 R2. Works if I execute the tests from a command line directly, doesn't 
work when triggered by Jenkins. Running Chrome 38.

Original comment by jim.lidd...@googlemail.com on 20 Oct 2014 at 11:42

GoogleCodeExporter commented 9 years ago 
Same here. Related https://code.google.com/p/chromium/issues/detail?id=422218

Original comment by Andrzej....@googlemail.com on 20 Oct 2014 at 1:16

GoogleCodeExporter commented 9 years ago 
If it helps anyone, I was able to find a standalone installer for Chrome 37 
here: http://www.alltypehacks.net/2013/07/download-new-full-google-chrome.html, 
and then followed the instructions here: 
http://blog.doofix.com/how-to-stop-google-chrome-from-automatic-update/ to 
disable auto-update until this is fixed.

Original comment by jim.lidd...@googlemail.com on 20 Oct 2014 at 1:47

GoogleCodeExporter commented 9 years ago 
Thanks for the links.  Rolling back seems to have worked for us.

Original comment by ja...@thebatesons.com on 20 Oct 2014 at 2:50

GoogleCodeExporter commented 9 years ago 
http://filehippo.com/download_google_chrome/history

Original comment by navi.heb...@gmail.com on 20 Oct 2014 at 3:28

GoogleCodeExporter commented 9 years ago 
Have encountered "Timed out receiving message from renderer: 600.000" since 
10/16 last week when the nodes in our selenium grid must have auto updated to 
Chrome 38.  I was able to isolate a very simple reproducible case to ensure it 
was not a problem emanating from the test suite design.

Selenium 2.43.1
ChromeDriver 2.11 (and 2.10)
Chrome 38.0.2125.104 m
Windows 7 SP1 Ent

Testing same Selenium and Windows versions against Chrome 37 works normally.  
Issue is only with Chrome 38.
---------------------

org.openqa.selenium.TimeoutException: timeout: Timed out receiving message from 
renderer: 600.000
  (Session info: chrome=38.0.2125.104)
  (Driver info: chromedriver=2.11.298604 (75ea2fdb5c87f133a8e1b8da16f6091fb7d5321e),platform=Windows NT 6.1 SP1 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 600.01 seconds
Build info: version: '2.43.1', revision: '5163bce', time: '2014-09-10 16:27:33'
System info: host: 'ESS2-1', ip: 'XXXXXXX', os.name: 'Windows 7', os.arch: 
'amd64', os.version: '6.1', java.version: '1.7.0'
Session ID: 7c823bae1338b50a360e3885117575f1
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{platform=XP, acceptSslCerts=true, javascriptEnabled=true, 
browserName=chrome, 
chrome={userDataDir=C:\Users\XXXXXXX\AppData\Local\Temp\scoped_dir4472_25989}, 
rotatable=false, locationContextEnabled=true, mobileEmulationEnabled=false, 
version=38.0.2125.104, takesHeapSnapshot=true, cssSelectorsEnabled=true, 
databaseEnabled=false, handlesAlerts=true, browserConnectionEnabled=false, 
nativeEvents=true, webStorageEnabled=true, applicationCacheEnabled=false, 
takesScreenshot=true}]
Command duration or timeout: 600.24 seconds
Build info: version: '2.43.1', revision: '5163bce', time: '2014-09-10 16:27:58'
System info: host: 'serat-MacBookPro1', ip: 'XXXXXXX', os.name: 'Mac OS X', 
os.arch: 'x86_64', os.version: '10.9.5', java.version: '1.6.0_65'
Session ID: fd7e68d0-7049-427d-aeff-878061fa0a96
Driver info: org.openqa.selenium.remote.RemoteWebDriver
Capabilities [{platform=XP, acceptSslCerts=true, javascriptEnabled=true, 
browserName=chrome, 
chrome={userDataDir=C:\Users\XXXXXXX\AppData\Local\Temp\scoped_dir4472_25989}, 
rotatable=false, locationContextEnabled=true, mobileEmulationEnabled=false, 
webdriver.remote.sessionid=fd7e68d0-7049-427d-aeff-878061fa0a96, 
version=38.0.2125.104, takesHeapSnapshot=true, cssSelectorsEnabled=true, 
databaseEnabled=false, handlesAlerts=true, browserConnectionEnabled=false, 
nativeEvents=true, webStorageEnabled=true, applicationCacheEnabled=false, 
takesScreenshot=true}]
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
    at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:204)
    at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:156)
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:599)
    at org.openqa.selenium.remote.RemoteWebDriver.get(RemoteWebDriver.java:304)
    at tests.DriverWrapperTest.DisplayWebDriverDetails(DriverWrapperTest.java:27)

Original comment by talkingt...@gmail.com on 21 Oct 2014 at 3:18

GoogleCodeExporter commented 9 years ago 
after upgrade to the new chrome version: 

(Session info: chrome=38.0.2125.104)
  (Driver info: chromedriver=2.9.248307,platform=Mac OS X 10.9.5 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 22 milliseconds
For documentation on this error, please visit: 
http://seleniumhq.org/exceptions/no_such_element.html
Build info: version: '2.39.0', revision: 
'14fa800511cc5d66d426e08b0b2ab926c7ed7398', time: '2013-12-16 13:18:38'
System info: host: 'XXXXXXXX.local', ip: 'XXXXXXXXX', os.name: 'Mac OS X', 
os.arch: 'x86_64', os.version: '10.9.5', java.version: '1.6.0_65'
Session ID: 7679bc70ea52c57515ae3714c81202e4
Driver info: org.openqa.selenium.chrome.ChromeDriver
Capabilities [{platform=MAC, acceptSslCerts=true, javascriptEnabled=true, 
browserName=chrome, 
chrome={userDataDir=/var/folders/sx/7l1kb5d148lbj04x5_m6wj7r0000gp/T/.org.chromi
um.Chromium.H1rSRA}, rotatable=false, locationContextEnabled=true, 
version=38.0.2125.104, takesHeapSnapshot=true, cssSelectorsEnabled=true, 
databaseEnabled=false, handlesAlerts=true, browserConnectionEnabled=false, 
nativeEvents=true, webStorageEnabled=true, applicationCacheEnabled=false, 
takesScreenshot=true}]
        at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:193)
        at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:145)
        at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:554)
        at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:307)
        at org.openqa.selenium.remote.RemoteWebDriver.findElementByTagName(RemoteWebDriver.java:372)
        at org.openqa.selenium.By$ByTagName.findElement(By.java:336)
        at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:299)

Original comment by alevtina...@siteminder.com on 21 Oct 2014 at 5:07

GoogleCodeExporter commented 9 years ago 
Also happens on Windows Server 2012 R2.

Also, upgrading to current beta or dev versions makes no difference; as of 
39.0.2171.27 dev-m there is no change.

Original comment by unwe...@gmail.com on 21 Oct 2014 at 7:40

GoogleCodeExporter commented 9 years ago 
Follow-up: I tried rolling my selenium nodes back to a VM template with Chrome 
v37.  I confirmed the version, used about:plugins to disable Google Update, 
restarted the browser, and checked Update was in fact disabled.  Then I went to 
About page, and witnessed Chrome ignoring that I disabled updates and it 
promptly installed v38 again.  So I cannot revert my nodes back to a state with 
Chrome 37, raising the urgency for a need for a fix in the chromedriver.

Original comment by talkingt...@gmail.com on 21 Oct 2014 at 4:04

GoogleCodeExporter commented 9 years ago 
More information and a workaround:  I use WinSW to run Selenium nodes as a 
Windows Service.  When run the Selenium nodes from a bat file so that browsers 
run in the foreground on the desktop, then the driver works and tests pass 
again.  The problem appears, for me, to occur when running Selenium node as 
Windows Service.  The hub always runs as a daemon on Linux.

Original comment by talkingt...@gmail.com on 21 Oct 2014 at 5:30

GoogleCodeExporter commented 9 years ago 
Same problem.  Really don't appreciate Google pulling an "Apple" and not 
letting you control your environment in the even they break it and fix it 
"eventually".  This issue is severely impacting our development process at the 
moment...

Original comment by mstrum...@synergydatasystems.com on 21 Oct 2014 at 7:30

GoogleCodeExporter commented 9 years ago 
I have this issue as well. W2008R2, Teamcity, ChromeDriver 2.10 and 2.11. 
Everything is ok from command line but no dice when run through TC Agent 
regardless of service account type or "allow to interact with desktop".

Original comment by faes...@gmail.com on 21 Oct 2014 at 7:34

GoogleCodeExporter commented 9 years ago 
I am facing the same issue with Chrome 38, on a Windows 7 VM machine when 
running the Selenium nodes as a windows service. Changing the ChromeDriver 
versions made no difference.

As a workaround I have to manually launch the Selenium nodes from a batch file 
if I want to use Chrome browsers, which is not convenient since the nodes 
require more monitoring this way. However I can still run the Selenium hub as a 
windows service with no issues

Original comment by dldz...@gmail.com on 21 Oct 2014 at 11:36

GoogleCodeExporter commented 9 years ago 
Same problem, running Selenium using XUnit from TeamCity.. works outside the 
service.  Will be rolling back Chrome until this is fixed.

Original comment by efergu...@ingrooves.com on 22 Oct 2014 at 2:06

GoogleCodeExporter commented 9 years ago 
@jim.lidd...@googlemail.com - thank you sir - you are my hero.  The links 
worked perfectly.  I don't know how you found that version 37 installer, but it 
worked like a champ.  I tried FileHippo, OldApps, and about 10 other downloads 
that didn't pan out.

Original comment by ke...@better-insights.com on 22 Oct 2014 at 3:27

GoogleCodeExporter commented 9 years ago 
We are experiencing the same issue. Solved temporary with chrome downgrade.

Original comment by m.no...@gmail.com on 22 Oct 2014 at 8:37

GoogleCodeExporter commented 9 years ago 
We're experiencing this too. Launching as service via TeamCity does not work 
with Google Chrome v38.

Original comment by conan...@gmail.com on 22 Oct 2014 at 11:24

GoogleCodeExporter commented 9 years ago 
Seeing the same issue running Protractor tests via Bamboo with the following 
configurations:

* Windows 2008 R2 / Windows 2012 R2
* chromedriver 2.10 & 2.11

Unfortunately I can't find a working link to a Chrome 37 installer, the all 
re-direct to latest.  Going to try to get this working with Chrome Canary for 
now.

Original comment by glenn.at...@gmail.com on 22 Oct 2014 at 6:36

GoogleCodeExporter commented 9 years ago 
Does any one have installer for chrome 37 that We could use.

Original comment by john.be...@gmail.com on 22 Oct 2014 at 7:16

GoogleCodeExporter commented 9 years ago 
I found that the link in #33 above worked 
http://code.google.com/p/chromedriver/issues/detail?id=928#c33

The link in #35 just redirects back to the latest chrome install.
http://code.google.com/p/chromedriver/issues/detail?id=928#c35

Original comment by glenn.at...@gmail.com on 22 Oct 2014 at 7:33