New issue
Advanced search Search tips

Issue 849800 link

Starred by 1 user

Issue metadata

Status: Unconfirmed
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Headless mode screenshots are double expected size

Reported by jbk...@gmail.com, Jun 5 2018

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.62 Safari/537.36

Steps to reproduce the problem:
1. Run command chrome --headless --screenshot --window-size=1280,1696 https://www.chromestatus.com/
2. Check saved screenshot dimensions

What is the expected behavior?
Dimensions of saved screenshot match window size specified.

What went wrong?
Dimensions of saved screenshots are double expected values.  ie for the specified window size 1280x1696 the produced screenshot is 2560x3392.

Did this work before? N/A 

Chrome version: 67.0.3396.62  Channel: stable
OS Version: OS X 10.13.5
Flash Version:
 
screenshot.png
236 KB View Download
Labels: Needs-Triage-M67
Components: Internals>Headless
Labels: Triaged-ET
Tried testing the issue on mac 10.13.3 using chrome reported version #67.0.3396.62 by running command as follows:
/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --headless --screenshot --window-size=1280,1696 https://www.chromestatus.com/

Observed the following error:
[0606/162158.397756:ERROR:xattr.cc(64)] setxattr org.chromium.crashpad.database.initialized on file /var/folders/_q/rf_5z5rx1r9dh7wt8n1x3jc80000gn/T/: Operation not permitted (1)
[0606/162158.399615:ERROR:file_io.cc(89)] ReadExactly: expected 8, observed 0
[0606/162158.403568:ERROR:xattr.cc(64)] setxattr org.chromium.crashpad.database.initialized on file /var/folders/_q/rf_5z5rx1r9dh7wt8n1x3jc80000gn/T/: Operation not permitted (1)
[0606/162158.437970:ERROR:gpu_process_transport_factory.cc(1017)] Lost UI shared context.
[0606/162200.776039:INFO:headless_shell.cc(590)] Written to file screenshot.png.

Hence, adding label TE-NeedsTriageHelp for further investigation from dev team as it seems to be related to headless which is out of TE-scope.

Thanks...!!
Labels: TE-NeedsTriageHelp

Sign in to add a comment