Closed
Bug 1109343
Opened 10 years ago
Closed 7 years ago
Browser timeline should be able to filter markers based on docshell
Categories
(DevTools :: Performance Tools (Profiler/Timeline), defect, P3)
DevTools
Performance Tools (Profiler/Timeline)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: vporof, Unassigned)
Details
I need this because:
* the netmonitor can be made faster
* I assume reflow/paints are the issue
* easiest way to test this is to open netmonitor, a browser timeline, hit reload and see what's happening
Currently, this doesn't work because the content and chrome (more specifically, our toolbox) markers are mixed up in the frontend. There's no way to filter between the two.
Let's assume I'm too lazy to use scratchpad to manipulate the netmonitor frontend myself.
Comment 1•10 years ago
|
||
I'm not sure to understand what you want exactly.
Markers are already scoped by a docshell. Except for paints, which include sub documents.
Reporter | ||
Comment 2•10 years ago
|
||
Moving into the Profiler component. Filter on GUTHRIE'S WAVY CAKES.
Component: Developer Tools: Timeline → Developer Tools: Profiler
Comment 3•10 years ago
|
||
In the browser toolbox, you're seeing both markers from network panel rendering, as well as the content that the netmonitor is measuring?
Comment 4•9 years ago
|
||
I'm not sure if this is still relevant -- and if so, how does it relate to the marker changes you're working on? I suspect we can close this, but want to make sure.
Flags: needinfo?(vporof)
Reporter | ||
Comment 5•9 years ago
|
||
Still an issue. As specified in comment 0, if the perf tool is opened in a browser toolbox, there's markers coming from everywhere, while I just want to focus on the ones coming from another toolbox, for example.
Flags: needinfo?(vporof)
Reporter | ||
Comment 6•9 years ago
|
||
Triaging. Filter on ADRENOCORTICOTROPIC (yes).
OS: Mac OS X → Unspecified
Priority: -- → P3
Hardware: x86 → Unspecified
Comment 7•7 years ago
|
||
This is re-filed as a new bug under the Gecko Profiler: Bug 1417976
Status: NEW → RESOLVED
Closed: 7 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
•