Issue metadata
Sign in to add a comment
|
Remote-debugging-port=9222 argument blocks Chrome from running in headless
Reported by
krystian...@gmail.com,
Jul 27 2017
|
||||||||||||||||||||||||
Issue description
UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.78 Safari/537.36
Steps to reproduce the problem:
The way I run selenium tests:
var options = new ChromeOptions();
if (ConfigurationManager.AppSettings["Headless"] == "true")
{
options.AddArgument("--window-size=1920x1080");
options.AddArgument("--headless");
options.AddArgument("--remote-debugging-port=9222");
}
driver = new RemoteWebDriver(new Uri("http://127.0.0.1:4444/wd/hub"), options
What is the expected behavior?
What went wrong?
When using options.AddArgument("--remote-debugging-port=9222") google chrome doesn't start
Did this work before? No
Chrome version: 60.0.3112.78 Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version:
,
Jul 28 2017
The issue seems to be out of TE-scope. hence, adding TE-NeedsTriageHelp for further investigation. Thanks...!!
,
Jul 28 2017
chromedriver uses the remote debugging API so you can't have the port open and also use selenium.
,
Jul 28 2017
Does this happen without --headless flag?
,
Jul 31 2017
"chromedriver uses the remote debugging API so you can't have the port open and also use selenium." So how can I debug when running selenium tests? I want to see what my chrome headless is rendering "Does this happen without --headless flag?" Yes
,
Jul 31 2017
Thank you for providing more feedback. Adding requester "dgozman@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 31 2017
Re #c5: unfortunately, there is no way as of today. Please see issue 129539 for more details. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by rsleevi@chromium.org
, Jul 27 2017