Compositor does too much work when scrolling a page on the compositor thread |
||||||
Issue descriptionThis should be a really cheap operation, but the compositor overhead seems really high especially with lots of layers. Some thoughts have been attached as blocking bugs. Other observations: * can we throttle begin main frame in some cases? * most updates are updates to the raster source offscreen (no raster work), can we commit these changes directly to the active tree more cheaply? * compositor frame deltas could help with small transform changes ⛆ |
|
|
,
Oct 8
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 8
|
|||
►
Sign in to add a comment |
||||||
Comment 1 by enne@chromium.org
, Oct 5 2017