Closed
Bug 833507
Opened 11 years ago
Closed 11 years ago
Integrated profiler should respect devtools.chrome.enabled pref
Categories
(DevTools :: Performance Tools (Profiler/Timeline), defect)
DevTools
Performance Tools (Profiler/Timeline)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: jimb, Unassigned)
References
Details
By default, the profiler removes samples that are running entirely in chrome code. This makes it difficult to find problems that are entirely chrome-related (in my instance, opening the Error Console janks badly when I have Google Maps open). Although we probably want a nicer UI in the long run, it would be spiffy if the profiler respected the devtools.chrome.enabled pref in the mean time.
Comment 1•11 years ago
|
||
Metrofx would really, really, really like this (and by that I mean the ability to profile chrome code is a requirement for shipping the 1.0) Metro does not support addons, so we are unable to take the current addon based workaround that desktop uses.
Comment 2•11 years ago
|
||
We landed another pref (see gear icon for DevTools) to display Gecko symbols. And we already display Chrome JS code.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•