FCP for about:blank is logged sometimes |
||
Issue descriptionFCP is bimodal in this benchmark (and some others): https://chromeperf.appspot.com/report?sid=0018fa66065b6809c3309c48a7bcd469bbe0ddafa306a183f149796abbf6a4a5 Looking at one trace where timeToFirstContentfulPaint_avg is low (https://console.developers.google.com/m/cloudstorage/b/chrome-telemetry-output/o/trace-file-id_53-2017-03-23_03-53-45-42656.html), FCP was logged twice, 348ms for https://twitter.com/nasa and 16ms for an empty URL. The latter was for a navigation to about:blank, but was not filtered as FrameLoader trace has empty URL "", not "about:blank". This should be a bug of trace logging.
,
Mar 31 2017
|
||
►
Sign in to add a comment |
||
Comment 1 by bugdroid1@chromium.org
, Mar 30 2017