New issue
Advanced search Search tips
Starred by 27 users

Issue metadata

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



Sign in to add a comment

Incomplete screenshots for large pages

Reported by s...@posterhaste.com, Aug 30 2017

Issue description

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

Steps to reproduce the problem:
1. Open the attached html file with Chrome
2. Open developer tools
3. Toggle "on" on the device toolbar
4. Click the "three dot" menu on the device toolbar and click "capture full-size screenshot"

What is the expected behavior?
A full-size screenshot (should be 6000x6000 pixels - or more if you have a retainer screen) showing a full gradient from top to bottom.

What went wrong?
An incomplete screenshot is saved, it is missing the bottom of the page. See attached image

Did this work before? N/A 

Chrome version: 60.0.3112.113  Channel: stable
OS Version: OS X 10.12.6
Flash Version: 

This seems to kick in on pages just under 6000x6000 pixels in size.

This was initially found when using Puppeteer to control Headless Chrome. The bug for Puppeteer can be found here:

https://github.com/GoogleChrome/puppeteer/issues/477
 
test-chrome.html
392 bytes View Download
test-chrome.html.png
2.9 MB View Download
Cc: eseckler@chromium.org
Components: Internals>Headless
Status: Available (was: Unconfirmed)
Looks like the tiles for the bottom of the page haven't finished rasterizing. Do things work if you try capturing a second screenshot after the first one?

The upcoming rendering control feature (issue 646774) should help with making this deterministic.
Cc: pfeldman@chromium.org
pfeldman@ mentioned something along these lines as well last week. Sounded like he was working on a workaround as well.

Comment 3 Deleted

that same problem, screenshots bigger that 6000x6000 are incomplete
Owner: lushnikov@chromium.org
Status: Assigned (was: Available)
any fix for this bug is planned?
I was able to reproduce the issue for much smaller resolutions (800X600), it can be reproduced in chromium by running it with --disable-gpu argument. referenced in here as well: https://github.com/GoogleChrome/puppeteer/issues/477

Sign in to add a comment