Issue metadata
Sign in to add a comment
|
12.4% regression in loading.desktop at 533798:533911 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Feb 6 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/16f7fd71840000
,
Feb 6 2018
📍 Found significant differences after each of 2 commits. https://pinpoint-dot-chromeperf.appspot.com/job/16f7fd71840000 Add HTTP-Bad Phase 3 experiment to field trial testing config by estark@google.com chromium @ 1b6c18abdf46a3f8ec7461070a4b20be10db89be cc: Ensure main frame not skipped on navigations. by khushalsagar@chromium.org chromium @ f60bbc668e29986e3f2dcc1f8fdfdbaba19deb02 Understanding performance regressions: http://g.co/ChromePerformanceRegressions
,
Feb 6 2018
,
Feb 6 2018
See https://bugs.chromium.org/p/chromium/issues/detail?id=764344. We consistently see that drawing an omnibox security chip on page load regresses this metric, but it's unclear why the security chip would impact time to first paint. We're going to need some help from test owners to figure that out.
,
Mar 20 2018
This has recovered |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Feb 6 2018