Issue 5351 in selenium: Strange error, chromedriver with --no-startup-window

[sele...@googlecode.com]

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

New issue 5351 by bushe...@gmail.com: Strange error, chromedriver with
--no-startup-window
http://code.google.com/p/selenium/issues/detail?id=5351

Hello!

I tried run tests using chromedriver in "background".
I specify "--no-startup-window" for this purpuse.


But I faced with strange issue. (please see above) If I run my application
without such capabilities All works fine.

My source code:

System.setProperty("webdriver.chrome.driver", "D:\\RR\\chromedriver.exe");
DesiredCapabilities capabilities = DesiredCapabilities.chrome();
capabilities.setCapability("chrome.switches",
Arrays.asList("--no-startup-window"));

WebDriver driver = new ChromeDriver(capabilities);
driver.get("http://ya.ru");
System.out.println(driver.getWindowHandle() + " Page title is: " +
driver.getTitle());

driver.close();
System.exit(0);



My NetBeans output:

Started ChromeDriver
port=1961
version=26.0.1383.0
log=C:\Users\unmanner\Documents\NetBeansProjects\seltest\chromedriver.log
[0318/002032:ERROR:automation_proxy.cc(319)] Channel error in
AutomationProxy.
Exception in thread "main" org.openqa.selenium.WebDriverException: Chrome
did not respond to 'GetChromeDriverAutomationVersion'. Elapsed time was 0
ms. (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 1.25 seconds
Build info: version: '2.31.0', revision: '1bd294d', time: '2013-02-27
20:53:56'
System info: os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1',
java.version: '1.7.0_17'
Driver info: org.openqa.selenium.chrome.ChromeDriver
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:525)
at
org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:187)
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.startSession(RemoteWebDriver.java:216)
at
org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:111)
at
org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:115)
at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:150)
at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:129)
at seltest.Seltest.main(Seltest.java:31)




My chromedriver.log:

[0.000][INFO]: ChromeDriver 26.0.1383.0 D:\RR\chromedriver.exe
[1.055][FINE]: Initializing session with capabilities {
"browserName": "chrome",
"chrome.switches": [ "--no-startup-window" ],
"platform": "ANY",
"version": ""
}
[1.055][INFO]: Launching chrome: "C:\Program Files
(x86)\Google\Chrome\Application\chrome.exe" --disable-hang-monitor
--disable-prompt-on-repost --dom-automation --full-memory-crash-report
--no-default-browser-check --no-first-run --disable-background-networking
--disable-sync --disable-translate --disable-web-resources
--safebrowsing-disable-auto-update
--safebrowsing-disable-download-protection
--disable-client-side-phishing-detection --disable-component-update
--disable-default-apps --enable-logging --log-level=1
--ignore-certificate-errors --no-startup-window about:blank
[1.136][INFO]: Connected to Chrome successfully. Version: 25.0.1364.172
[1.157][INFO]: Chrome shutdown



Thanks you for support!


--
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: WorkingAsIntended
Labels: -Status-Untriaged Component-WebDriver Browser-Chrome

Comment #1 on issue 5351 by jmle...@gmail.com: Strange error, chromedriver
with --no-startup-window
http://code.google.com/p/selenium/issues/detail?id=5351

Much like --disable-javascript, the chromedriver will not work if you use
--no-startup-window. It needs to launch a window to establish the
connection with the AutomationProxy.