Closed
Bug 1160812
(perf-allocations)
Opened 10 years ago
Closed 2 years ago
[meta] Performance Tool Allocations
Categories
(DevTools :: Performance Tools (Profiler/Timeline), enhancement, P3)
DevTools
Performance Tools (Profiler/Timeline)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: jsantell, Unassigned)
References
Details
(Keywords: meta)
No description provided.
Reporter | ||
Updated•10 years ago
|
Reporter | ||
Updated•10 years ago
|
Alias: perf-memory
Reporter | ||
Updated•10 years ago
|
No longer depends on: 1152397
Summary: [meta] Performance Tool Memory → [meta] Performance Tool Allocations
Reporter | ||
Comment 1•10 years ago
|
||
Let's use this to track any outstanding work needed for using allocations, and if we can get this in Fx41.
Reporter | ||
Updated•10 years ago
|
Updated•9 years ago
|
Alias: perf-memory → perf-allocations
Comment 2•9 years ago
|
||
Triaging. Filter on ADRENOCORTICOTROPIC (yes).
Priority: -- → P1
Version: 37 Branch → unspecified
Comment 3•9 years ago
|
||
Don't think this meta bug is relevant at this time.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Comment 4•9 years ago
|
||
You don't think having a meta bug to track bugs in the allocations view is relevant? I could certainly see how it might not be a priority, but how could it be irrelevant?
Flags: needinfo?(vporof)
Comment 5•9 years ago
|
||
Don't want us to have bugs we're not actively looking at (in this component at least). None of these bugs have been worked on in a very long time (7+ months). I think meta bugs should be for things we're actively working on, otherwise they end up not being updated as new bugs get filed. In the interest of easier triage, I closed this.
That being said, my views on meta bugs aren't absolute. If it makes sense keeping this one open, let's do it.
Status: RESOLVED → REOPENED
Flags: needinfo?(vporof)
Resolution: FIXED → ---
Updated•7 years ago
|
Updated•6 years ago
|
Product: Firefox → DevTools
Updated•2 years ago
|
Severity: normal → S3
Comment 6•2 years ago
|
||
This report is related to the old DevTools Profiler.
The Performance panel now points to the new Firefox profiler available at profiler.firefox.com
Closing as Invalid bug
Status: REOPENED → RESOLVED
Closed: 9 years ago → 2 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•