Closed
Bug 1730108
Opened 3 years ago
Closed 3 years ago
Introduce a test to track memory while opening and closing the browser console
Categories
(DevTools :: Console, task)
DevTools
Console
Tracking
(firefox94 fixed)
RESOLVED
FIXED
94 Branch
Tracking | Status | |
---|---|---|
firefox94 | --- | fixed |
People
(Reporter: ochameau, Assigned: ochameau)
References
(Blocks 1 open bug)
Details
(Whiteboard: dt-perf-stability-mvp)
Attachments
(1 file)
Similarly to bug 1727571, we should probably have a test covering leaks happening after a browser console close.
We should ensure that everything is cleared when the Browser Console is closed.
It may also highlight some code that keeps running even after the tool is closed.
Assignee | ||
Comment 1•3 years ago
|
||
The test currently reports 55657 objects being leaked on mozilla-central.
This is slightly reduced down to 55161 objects when applying all patches described on bug 1682212 comment 47.
And no improvement are reported from patch of bug 1729925, which are too specific to the inspector and toolbox.
I imagine we may also benefit from having a copy of browser_allocations_reload.js to track the console leaks.
Assignee | ||
Comment 2•3 years ago
|
||
Updated•3 years ago
|
Whiteboard: dt-perf-stability-mvp
Pushed by apoirot@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/ed63b5ba125f
[devtools] Introduce a test to track memory while opening and closing the browser console. r=nchevobbe
Comment 4•3 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox94:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 94 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•