35% of the main thread time scrolling iron-list is VisibleUnits::canonicalPosition |
|||||||||
Issue descriptionGoogle Chrome 53.0.2773.0 (Official Build) canary (64-bit) Revision ced2fcee2c85702055d028f4e3e48c5a75a7e41c-refs/heads/master@{#400610} OS Mac OS X What steps will reproduce the problem? (1) Load https://elements.polymer-project.org/elements/iron-list?view=demo:demo/index.html&active=iron-list (2) Open about:tracing and record all. (3) Scroll the page up and down. Notice the huge time slice for This is extra surprising because I have nothing selected, the page is freshly loaded, and I'm just scrolling up and down. Why are we spending so much time in there?
,
Jun 20 2016
Sigh, reloading the page and tracing again I can't get this to repro. When it did repro it happened every time though. I've seen this same super expensive VisibleUnits thing before which makes me think there's some bug with a race maybe?
,
Jun 21 2016
,
Jun 21 2016
The page you point: https://elements.polymer-project.org/elements/iron-list?view=demo:demo/index.html&active=iron-list shows a card(see attached image). Thus I couldn't find any scrolling and reproduce. I guess the issue is on a page of the six demos. Elliott, could you explain more?
,
Jun 22 2016
There are two suspects: 1. FlatTreeTraversal::parent, child, nextSibling, previousSibling 2. Many calls of Document::updateStyleAndLayoutTreeIgnorePendingStylesheets() - When there are style sheet placeholder and pending HTML imports, USLIP() does layout for every call due by setNeedsStyleRecalc(SubtreeStyleChange, StyleChangeReasonForTracing::create(StyleChangeReason::CleanupPlaceholderStyles)); Suspects 2 can explain esprehn@'s experience in #c2.
,
Jun 22 2016
There was nothing under that slice, and it was every frame. It wasn't a large style recalc or layout, it was the code inside VisibleUnits::canonicalPosition doing something expensive like walking the whole DOM or layout tree repeatedly. Of course I can't reproduce now, which makes me think this is a race condition. Once you get into the state where this happens every frame we pump has this at the start of it though.
,
Jul 4 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 12 2016
,
Mar 7 2017
,
Oct 4 2017
,
Oct 4
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 5
|
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by esprehn@chromium.org
, Jun 20 20163.2 MB
3.2 MB Download