Before filing an issue, please read the page at
http://code.google.com/p/selenium/wiki/SeleniumHelp This contains lot of
information about how best to get help, and tells you what we need to know.

Still here? We know that bugs are frustrating and annoying things. We also
know that you've probably spent ages trying to figure out what's wrong. The
more information you give us now, the more likely it is that we'll be able
to help.

What steps will reproduce the problem?
1. Run ChromeDriver 2.11 with Chrome 38 using Task Scheduler in association with a
service account. Or run via Team City with SYSTEM account.

What is the expected output? What do you see instead?
Expect the tests to run, instead get the below (TeamCity):

Test(s) failed. OpenQA.Selenium.WebDriverException : The HTTP request to the remote
WebDriver server for URL http://localhost:65460/session/bc6f423fc15199174b531f02ee6bd72a/elements
timed out after 60 seconds.
  ----> System.Net.WebException : The operation has timed out
   at OpenQA.Selenium.Remote.HttpCommandExecutor.CreateResponse(WebRequest request)
   at OpenQA.Selenium.Remote.DriverServiceCommandExecutor.Execute(Command commandToExecute)
   at OpenQA.Selenium.Remote.RemoteWebDriver.Execute(String driverCommandToExecute,
Dictionary`2 parameters)
   at OpenQA.Selenium.Remote.RemoteWebDriver.FindElements(String mechanism, String
value)
   at OpenQA.Selenium.By.FindElements(ISearchContext context)
   at Project.Tests.Acceptance.XyzTests.jobresults_page1_should_have_paging_bar_with_10_page_links()
in e:\BuildAgent\work\1224369d9b0230b4\src\Project.Tests.Acceptance\Tests.cs:line 54
--WebException
   at System.Net.HttpWebRequest.GetResponse()
   at OpenQA.Selenium.Remote.HttpCommandExecutor.CreateResponse(WebRequest request)

Or, when running via Perl:
malformed JSON string, neither array, object, number, string or atom, at character
offset 0 (before "read timeout at C:/P...") at RemoteConnection.pm line 102.

i.e in both cases, timeouts. Not a single test step runs.

Selenium version: 2.43.1
OS: Windows 2012 Datacentre
Browser: Chrome
Browser version: 38
ChromeDriver Version: 2.11

Note that Chrome version 37 is OK.

Note that Chrome version 38 is OK when run via interactive mode - i.e. a user logged
into the Server kicks off the test using their own account in interactive mode (you
see Chrome open on the screen and run). If that same user tries to run the tests via
Task Scheduler, even using their own credentials (instead of the normal service account),
it fails.

Other information: PhantomJS with ChromeDriver 2.11 / Selenium Server 2.43.1 is OK.


Please provide any additional information below. A sample reduced test
case, or a public URL that demonstrates the problem will intrigue our merry
band of Open Source developers far more than nothing at all: they'll be far
more likely to look at your problem if you make it easy for them!