PendingTree's UpdateDrawProperties is unnecessary for submitting current compositorFrame.
Reported by
perryuw...@tencent.com,
Nov 4 2016
|
||||||||
Issue descriptionSteps to reproduce the problem: 1. My device is Samsung Galaxy S Ⅲ（i9300） 2. App is Android webview shell (56.0.2908.3) 3. Visit url sina.cn 4. Attached file is a trace. What is the expected behavior? What went wrong? pendingTree's UpdateDrawProperties is a time-consuming task. Did this work before? N/A Chrome version: 56.0.2908.3 Channel: n/a OS Version: 4.4 Flash Version: Shockwave Flash 21.0 r0
,
Nov 4 2016
it's not happening in DemandDrawHw, so it's not inside the draw itself but pending tree UpdateDrawProperties has to happen at some point on the compositor thread, and we are not going to re-order events on the compositor thread, so UI has to wait for the entire compositor thread queue to flush I guess smoothness might change the heuristics here, but we've had that discussion before for webview
,
Nov 4 2016
Context here is https://codereview.chromium.org/2470333002/. Now that I know what to look for, I did notice frames with pending trees. So never mind #2
,
Nov 4 2016
ok, still decided to not do anything on code review |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by rsgav...@chromium.org
, Nov 4 2016