Closed Bug 923396 Opened 10 years ago Closed 6 years ago

Use source maps in the profiler


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

24 Branch


(Not tracked)



(Reporter: carl, Unassigned)


(Blocks 1 open bug)


(Whiteboard: [bugday-20131007])


(1 file)

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.71 Safari/537.36

Steps to reproduce:

Enable source maps.
Run a profiler.
Navigate the tree (combined js files are listed)
Click the arrow to navigate to source.

Actual results:

It switches to the debugging console with no file selected.
Debugging console shows only source maps.

Expected results:

It would be nice if it displayed source maps in the tree.
At the very least, it should translate from the combined file to the source map in the debugging console.
See Also: → 670002
See Also: → 856875, 886233
Component: Untriaged → Developer Tools
Whiteboard: [bugday-20131007]
From dup bug 923858:
> Nick Fitzgerald [:fitzgen], comment 0:
> We should use source maps to get the original url/line/column/name of each
> function call in the profiler.
Component: Developer Tools → Developer Tools: Profiler
Ever confirmed: true
Also copying the P3 assigned by Anton Kovalyov (:anton, @valueof) in the other bug...
Priority: -- → P3
Summary: Source maps are not working in the profiler → Use source maps in the profiler
OS: Mac OS X → All
Hardware: x86 → All
Assignee: nobody → jsantell
Assignee: jsantell → nobody
Priority: P3 → P5
I have a WIP patch from a while back that I'm going to attach.
Haven't really tried it and didn't write a test case.
We're not planning on completing this work. Source maps will most likely be handled differently in the new recording panel. We'll file new bugs once we have the work figured out for how to implement that.
Closed: 6 years ago
Resolution: --- → WONTFIX
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.