Scrolling large web page corrupts graphics |
||||||||||||||
Issue descriptionReproducible on: Chrome OS kevin R61.0.3163.93 / Platform 9765.64.0 (also reproducible on cave, bob) Chrome Linux: 61.0.3163.100 (Official Build) (64-bit) Chrome Mac: 60.0.3112.113 (Official Build) (64-bit) Reproduce steps: 1. Download and open big.html file in the attachment. 2. Set page scale to 100%. 3. Press end key to scroll to the end (or search + right arrow on ChromeOS). 4. The page graphics content after tile with y index 65535 is corrupted. Kevin trigger this issue easier because it is 200% UI scale when screen resolution is not set to 2400x1600. The graphics corrupted after the div with number 32767 on kevin. Seems chrome has a tile y index limitation on 65536, is it known limitation?
,
Sep 20 2017
,
Sep 20 2017
I repro this in dev image of 9756.1.0 / 61.0.3159.8.
,
Sep 20 2017
Repro this in dev image of 9693.1.0 / 61.0.3144.0. Cannot repro this in dev image of 9672.0.0 /61.0.3136.5. I will get "Page Unresponsive" error when scrolling the text file very fast. No renderering error. There are several canary builds I can continue bisecting.
,
Sep 21 2017
I can repro this issue on kevin dev image R58.9334.24.0, R59.9460.76.0, R60.9592.96.0, ... that's every kevin dev I tested. cannot repro on bob R63 tot. about the previous culprit CLs, the previous bisection was done on a profile with Traditional Chinese language, so it's affected by the CJK font change: https://chromium-review.googlesource.com/c/chromiumos/overlays/chromiumos-overlay/+/576708 https://chrome-internal-review.googlesource.com/c/chromeos/overlays/chromeos-overlay/+/414228
,
Sep 21 2017
Bob might not have the same smooth scrolling settings as Kevin -- I think the default changes when you have the hidpi flag set -- I meant to file a bug to make them the same but forgot about that
,
Sep 21 2017
vovoy@, is it R58.9334.24.0 or R58.9334.74.0?
,
Sep 21 2017
R58.9334.24.0
,
Sep 22 2017
,
Sep 22 2017
,
Sep 22 2017
,
Sep 22 2017
,
Sep 22 2017
,
Sep 22 2017
Issue 766243 has been merged into this issue.
,
Sep 22 2017
vovoy@, Good finding! I can repro this on Chrome (61.0.3163.91) on linux. It will break beyong y index is 65535. So this is not ChromeOS issue.
,
Sep 22 2017
,
Sep 22 2017
I thought we limit the size of the page because of this.
,
Sep 22 2017
,
Sep 22 2017
Probably a result of us using 16 bits for the TileMap key: https://cs.chromium.org/chromium/src/cc/tiles/picture_layer_tiling.h?l=76
,
Sep 22 2017
,
Sep 22 2017
danakj@, do you think we should be limiting the page size? That would be a Layout issue, I think, and not clear how to implement it since we don't know how big the page is until after we have laid it out, and then we have no easy way of avoiding creating display item list content outside of the limit size. If we just threw away anything with a cull rect outside the bound we might remove a background layer entirely, rather than clipping it like we should. Can't CC just never try to create and raster tiles outside the range?
,
Sep 22 2017
There's some size limiting in GraphicsLayer I'm pretty sure... unless it broke or was removed? Maybe cc changes to not support even the size occured tho.
,
Sep 22 2017
There have been discussions in the past about limiting scrolling to 2^24px. See crbug.com/446530.
,
Sep 24 2017
|
||||||||||||||
►
Sign in to add a comment |
||||||||||||||
Comment 1 Deleted