Closed
Bug 1196862
Opened 9 years ago
Closed 2 years ago
Serve allocation data after recording is ended
Categories
(DevTools :: Performance Tools (Profiler/Timeline), defect, P3)
DevTools
Performance Tools (Profiler/Timeline)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: jsantell, Unassigned)
References
Details
Right now, we serve allocation data realtime like we do markers, but don't do anything with it until we're done recording. This can be a huge overhead (see attachment, was running the GC octane test), accounting for a giant gap of uninstrumented framerate drops (call tree shows its all in devtools code), similar to the memory over time recording overhead. Seems worse though. Luckily we can serve it when we're done.
We should have this for Fx43 for allocations launch, this is pretty crucial.
Reporter | ||
Updated•9 years ago
|
No longer blocks: perf-tools-fx43
Reporter | ||
Updated•9 years ago
|
Blocks: perf-tools-fx44
Reporter | ||
Updated•9 years ago
|
No longer blocks: perf-tools-fx44
Reporter | ||
Updated•9 years ago
|
Assignee: jsantell → nobody
Status: ASSIGNED → NEW
Comment 1•9 years ago
|
||
Triaging. Filter on ADRENOCORTICOTROPIC (yes).
Priority: -- → P3
Version: 41 Branch → unspecified
Updated•6 years ago
|
Product: Firefox → DevTools
Updated•2 years ago
|
Severity: normal → S3
Updated•2 years ago
|
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•