chromedriver does not return if --remote-debugging-port argument is specified

[GoogleCodeExporter]

See http://goo.gl/ll2FvQ for common issues.

Issue Description:
I am trying to automate my web-app using selenium. If I launch chrome.exe using 
chromeOptions and provide the argument --remote-debugging-port=xxyy through 
options.add_argument, then chrome gets launched. However, chromedriver does not 
return. It returns after a timeout of approx 30secs with the error msg which 
says "chrome not reachable"

chromedriver version: 2.10
chrome version: 36.0.1985.143 m
selenium version: 2.42.1

From what I see in the logs, chromedriver launches chrome.exe with the 
remote-debugging-port argument that I provided. However, chromedriver keeps 
sending the devtools request on a port which it generates uniquely. See 
attached log file qc1.log

Steps to reproduce (if relevant, you MUST provide a simplified html page or
link to public site):
<enter repro steps here>

-----Other helpful tips:
Attach your chromedriver log with verbose logging enabled (see
http://goo.gl/5Sx8mC for how to do this).

Original issue reported on code.google.com by 11mohitb...@gmail.com on 13 Aug 2014 at 12:53

Attachments:

• qc1.log

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Same issue here
[7.552][INFO]: Launching chrome: "<path_to_chrome>" 
--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\Dick\AppData\Local\Temp\scoped_dir9324_28935\internal
" --log-level=0 --metrics-recording-only --no-first-run --password-store=basic 
--remote-debugging-port=9555 --safebrowsing-disable-auto-update 
--safebrowsing-disable-download-protection --test-type=webdriver 
--url=file:///index.html --use-mock-keychain 
--user-data-dir="C:\Users\Dick\AppData\Local\Temp\scoped_dir9324_25757" data:,
[7.559][DEBUG]: DevTools request: http://127.0.0.1:12559/json/version
[8.558][DEBUG]: DevTools request failed
[8.609][DEBUG]: DevTools request: http://127.0.0.1:12559/json/version
....
[75.037][INFO]: RESPONSE InitSession unknown error: Chrome failed to start: 
exited normally

Original comment by dvdbrin...@gmail.com on 16 Jan 2015 at 2:30

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

#2  you may have different issue 

launch chrome with command line

"<path_to_chrome>" --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\Dick\AppData\Local\Temp\scoped_dir9324_28935\internal
" --log-level=0 --metrics-recording-only --no-first-run --password-store=basic 
--remote-debugging-port=9555 --safebrowsing-disable-auto-update 
--safebrowsing-disable-download-protection --test-type=webdriver 
--url=file:///index.html --use-mock-keychain 
--user-data-dir="C:\Users\Dick\AppData\Local\Temp\scoped_dir9324_25757" data:

Original comment by andrewch...@chromium.org on 22 Jan 2015 at 11:44

[GoogleCodeExporter]

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

• Changed state: Unconfirmed