Closed Bug 1167351 Opened 9 years ago Closed 9 years ago

Display JS function name in markers

Categories

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

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jsantell, Assigned: jsantell)

References

Details

Front end for bug 1050500
Assignee: nobody → jsantell
Status: NEW → ASSIGNED
Depends on: 1050500
I think there's nothing to do here because the function-to-be-called is
represented as a sort of phony stack frame.  This is slightly weird but
it came from trying to also deal with the async stack; which has subsequently
been postponed.
ah, so we won't have the entry JS function name here with bug 1050500? Or only for async stacks?
(In reply to Jordan Santell [:jsantell] [@jsantell] from comment #2)
> ah, so we won't have the entry JS function name here with bug 1050500? Or
> only for async stacks?

We'll have the name, but the code in marker-details.js will display it without
any further changes, as it will look like a stack with a single frame.
Marker views are a lot nicer now, more declarative, so taking this single frame stack and turning it into be displayed is easy
No longer blocks: perf-40-uplifts
I think this is good to go in that case, TT can you confirm?
Flags: needinfo?(ttromey)
Yes, I think this bug was already fixed by bug 1050500.
Really clearing needinfo.
Flags: needinfo?(ttromey)
Resolving this in that case
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.