1164333 - Missing JS marker

Status: RESOLVED INVALID

(DevTools :: Performance Tools (Profiler/Timeline), defect, P3)

Description

[Jordan Santell [:jsantell] [@jsantell]]

Attachment: 4s of JS with no markers

In this browser toolbox recording, between 2500ms and 6500ms, we have no record of what's occurring here. It looks as if it's kicked off by some DOM events and handlers, but then there's nothing for this blocking 4 second range.

Should the handler/event markers stretch this duration? Or is this something else missing that should be instrumented?

Comment 1

[Jordan Santell [:jsantell] [@jsantell]]

Attachment: metaprofile_v3.json

Corresponding profile if you want to load it up to look yourself -- this has frame deduping, so you'll need a build after yesterday.

Comment 2

[Jordan Santell [:jsantell] [@jsantell]]

ni?ing Nick and Tom, seeing this more especially with platform code (the above profile is measuring the perf tool itself via browser toolbox)

Comment 3

[Nick Fitzgerald [:fitzgen] [⏰PST; UTC-8]]

Did you verify that there are no markers overlapping that duration in the profile? In other words, you have verified this to be a platform bug, and not something else?

Comment 4

[Jordan Santell [:jsantell] [@jsantell]]

It's not a rendering issue if that's what you're asking -- there are 0 JS markers between the range selected in the attached profile

Comment 5

[Nick Fitzgerald [:fitzgen] [⏰PST; UTC-8]]

(In reply to Jordan Santell [:jsantell] [@jsantell] from comment #4)
> It's not a rendering issue if that's what you're asking -- there are 0 JS
> markers between the range selected in the attached profile

Is this reproducible? Test case? STR?

Comment 6

[Jordan Santell [:jsantell] [@jsantell]]

STR:
Open perf tools. Import a large recording previously recorded (octane works well).
Open browser toolbox. Start recording chrome code here.
In the regular toolbox, click from "Waterfall" to "JS Call Tree" to start the rendering of the call tree.
After the call tree is rendered, stop recording in the browser toolbox.


The attached recording is of a similar recording, where it seems the js::RunScript or GeckoProcessEvents areas don't have JS markers, which may be easier viewing rather than doing all the above to reproduce a profile to start

Comment 7

[Victor Porof [:vporof][:vp]]

Triaging. Filter on ADRENOCORTICOTROPIC (yes).

Comment 8

[Jan Honza Odvarko [:Honza] (always need-info? me)]

This report is related to the old DevTools Profiler.
The Performance panel now points to the new Firefox profiler available at profiler.firefox.com
Closing as Invalid bug