Display (idle) nodes in the flamegraph for the new performance tool

RESOLVED FIXED in Firefox 38

Status

()

Firefox
Developer Tools: Performance Tools (Profiler/Timeline)
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: vporof, Assigned: vporof)

Tracking

unspecified
Firefox 38
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

Comment hidden (empty)
(Assignee)

Updated

3 years ago
Blocks: 1075567
(Assignee)

Updated

3 years ago
Assignee: nobody → vporof
Status: NEW → ASSIGNED
(Assignee)

Comment 1

3 years ago
Created attachment 8547676 [details] [diff] [review]
v1
Attachment #8547676 - Flags: review?(jsantell)
Attachment #8547676 - Flags: review?(jsantell) → review+
Again for the options, do we want to expose these at some point in a settings drop down, like the debugger has? Or are these just for the brave config-editors?
(Assignee)

Comment 3

3 years ago
(In reply to Jordan Santell [:jsantell] [@jsantell] from comment #2)
> Again for the options, do we want to expose these at some point in a
> settings drop down, like the debugger has? Or are these just for the brave
> config-editors?

Yes.

Take that as an "I don't know".

I would vote for exposing *some* of those options in a gear menu. Maybe sometimes you don't want to flatten recursion, for example.
Can always start with just plain old prefs and build UI later.
(Assignee)

Comment 5

3 years ago
(In reply to Nick Fitzgerald [:fitzgen] from comment #4)
> Can always start with just plain old prefs and build UI later.

Which is what we're doing.
https://hg.mozilla.org/mozilla-central/rev/f5053a5e716a
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
Whiteboard: [fixed-in-fx-team]
Target Milestone: --- → Firefox 38
You need to log in before you can comment on or make changes to this bug.