New issue
Advanced search Search tips

Issue 792497 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 809833
Owner:
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

FMP in loading_metric is not getting computed on some traces.

Project Member Reported by mythria@chromium.org, Dec 6 2017

Issue description

In the attached trace first meaningful paint is not computed correctly. We get an empty list for FMP with the attached trace. I looked into it a bit, and it appears that frameToNavStartEvents is empty and hence we dont add any FMP candidates.
(https://cs.chromium.org/chromium/src/third_party/catapult/tracing/tracing/metrics/system_health/loading_metric.html?q=loading_metri&sq=package:chromium&l=362)

I am not sure why the list is empty though. Any ideas on what could have gone wrong? Happy to provide any further information required.

 
http___maps_google_co_jp_maps_search_restaurant_tokyo_2017-12-05_22-15-52_91089.html
4.4 MB View Download
Also forgot to mention, this happens quite consistently with maps page in v8.runtimestats.top_25 benchmark on the cold run. The attached trace is from one such run.
Cc: ksakamoto@chromium.org tdres...@chromium.org kouhei@chromium.org
Components: -Speed>Telemetry Speed>Metrics
Cc: mythria@chromium.org

Comment 5 by dproy@chromium.org, Dec 6 2017

It seems the trace event 'navigationStart' with category 'user_timing' is missing from the trace. I believe this is emitted here: https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/loader/DocumentLoadTiming.cpp?type=cs&q=navigationStart+blink.user_timing&sq=package:chromium&l=120

I can reproduce the problem on Tip of Tree chrome: 
1. Restart chrome (do not use an already running instance)
2. navigate to about:tracing. Select all the default categories. Start recording.
3. Open a new tab. Type in "google.com". Press Enter.
4. Wait a few seconds, then go back to about:tracing. Stop recording.
5. Open the metrics panel on the right. See everything is empty. You can also verify that no 'navigationStart' event is in the trace. 

What's surprising is if you now start recording again, go back to the google tab, and refresh it, and then stop recording, the navigation start event is now there and you see the metrics in the metrics panel.

Somehow the trace event is not emitted in the first case, and I didn't get a chance to debug yet why. 
Owner: dproy@chromium.org
Status: Assigned (was: Untriaged)
Deep, are you a good owner for this?

Comment 7 by dproy@chromium.org, Jan 4 2018

I will look into this more and assign to a more appropriate owner if needed.

Comment 8 by dproy@chromium.org, Feb 26 2018

Mergedinto: 809833
Status: Duplicate (was: Assigned)

Sign in to add a comment