Headless chrome does not print output, or files (Windows)
Reported by
jari.pen...@gmail.com,
Jul 26 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.78 Safari/537.36 Steps to reproduce the problem: PS C:\> taskkill /f /im chrome.exe PS C:\> where.exe chrome C:\Program Files (x86)\Google\Chrome\Application\chrome.exe PS C:\> [System.Diagnostics.FileVersionInfo]::GetVersionInfo($(where.exe chrome)).FileVersion 60.0.3112.78 PS C:\> chrome --headless --disable-gpu --dump-dom https://www.chromestatus.com/ PS C:\> chrome --headless --disable-gpu --repl https://www.chromestatus.com/ There is no output, it just exits. Print to pdf likewise does not produce files. What is the expected behavior? I should get some output on the shell, and files on the folder. What went wrong? There is no output or files. Did this work before? N/A Does this work in other browsers? N/A Chrome version: 60.0.3112.78 Channel: stable OS Version: 10.0 Flash Version: This might be a problem with my setup, I will investigate this and post my findings in here if others encounter this.
,
Jul 27 2017
,
Jul 31 2017
Hi, note that if you execute headless in windows, the default output directory will be where the executable runs, so if you don't have permissions it will not be able to output to that directory (in this case, to C:\Program Files (x86)\Google\Chrome\Application\) You can setup --dump-dom=c:/file/path or --print-to-pdf=c:/file/path to test that that's the issue
,
Aug 13 2017
It does not explain why -repl switch does not work on Windows at all. It should start a prompt but nothing appears, it just exits. I did get the output to file working with your advice.
,
Aug 21 2017
The way Chrome works on Windows makes --repl not work on --headless, unfortunately. You can always open the remote-debugging-port and user the devtools interface. |
||||
►
Sign in to add a comment |
||||
Comment 1 by manoranj...@chromium.org
, Jul 27 2017