No firstMeaningfulPaint trace event emitted on chrome://md-settings/ |
||||||
Issue descriptionWe're using lighthouse to extract metrics from chrome://settings but no fMP trace event is emitted. The user_timing category is in the trace. Plenty of fCP, but no fMP present. Perhaps something odd about the network detection? A sample trace attached.
,
Dec 14 2016
And another better trace.. :) Now including the 'loading' trace category. no sign of fMPCandidates events.
,
Dec 15 2016
This is similar to Issue 659021 . FMPDetector detected "network stable" before the first paint, and stopped observing layouts.
,
Dec 15 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/2b891d60b92a6066fa1620794e244ef6e0ce65e2 commit 2b891d60b92a6066fa1620794e244ef6e0ce65e2 Author: ksakamoto <ksakamoto@chromium.org> Date: Thu Dec 15 09:25:57 2016 [FirstMeaningfulPaint] Do not stop observing layouts before FirstContentfulPaint This should mitigate a bug that FirstMeaningfulPaint is reported too soon (or not reported) on some CPU-heavy pages, because network idle is detected while CPU is busy running scripts. BUG= 659021 , 674228 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 Review-Url: https://codereview.chromium.org/2581633002 Cr-Commit-Position: refs/heads/master@{#438791} [modify] https://crrev.com/2b891d60b92a6066fa1620794e244ef6e0ce65e2/third_party/WebKit/Source/core/paint/FirstMeaningfulPaintDetector.cpp [modify] https://crrev.com/2b891d60b92a6066fa1620794e244ef6e0ce65e2/third_party/WebKit/Source/core/paint/FirstMeaningfulPaintDetectorTest.cpp
,
Dec 16 2016
I believe this is now fixed.
,
Dec 16 2016
most good. thank you! |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by paulir...@chromium.org
, Dec 14 20161.3 MB
1.3 MB Download