Open Bug 1546520 Opened 6 years ago Updated 3 years ago

TTFI marker created outside of the profiler's time profiling range

Categories

(Core :: Gecko Profiler, defect, P3)

defect

Tracking

()

Future
Tracking Status
firefox68 --- affected

People

(Reporter: Harald, Unassigned)

Details

Attachments

(1 file)

Attached image image.png

Profiled CNN and got this stray TTFI marker: https://perfht.ml/2UATIY3

{
  "start": 35135.42007564062,
  "dur": 9788.201958000005,
  "name": "TTFI",
  "data": {
    "type": "Text",
    "startTime": 35135.42007564062,
    "endTime": 44923.622033640626,
    "docShellId": "{6601c0fa-923f-254f-936d-815c26ebaaf8}",
    "docshellHistoryId": 1,
    "name": "TTFI after 9788ms (LongTask was at 9788ms) for URL https://www.cnn.com/"
  },
  "title": null
}

Might be related to the time-based buffer work.

Component: Performance → Performance Tools (Profiler/Timeline)
Product: Core → DevTools
Target Milestone: --- → Future
Version: Trunk → unspecified
Component: Performance Tools (Profiler/Timeline) → Gecko Profiler
Product: DevTools → Core

Hrlad, can you tell us more? Does it make sense that we see a 11 seconds delay in starting the capture? Was the browser and the computer especially busy?

I did stop the profiler quickly before, which should have flushed the previous recordings. Will try to reproduce.

Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: