Closed
Bug 1242018
Opened 10 years ago
Closed 10 years ago
Memory is retained when loading snapshots for too long
Categories
(DevTools :: Memory, defect, P3)
DevTools
Memory
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: jsantell, Unassigned)
Details
STR:
* Start a fresh firefox
* Open memory tools and import attachment from bug 1226319,
* Let it finish loading and close devtools
ER: Firefox that only has a default tab open, and nothing else, is taking up a reasonable amount of ram.
AR: For a few minutes, the instance of Firefox with just a default tab open, and devtools closed, can take several GBs of memory. Eventually it gets cleared, but it's a bit too long, like atleast a few minutes. Maybe we can force a GC when closing the toolbox, or clearing out snapshots?
| Reporter | ||
Comment 1•10 years ago
|
||
Comment 2•10 years ago
|
||
If you go to about:memory and do a "minimize memory usage" does it go away immediately?
Flags: needinfo?(jsantell)
Updated•10 years ago
|
Priority: -- → P3
| Reporter | ||
Comment 3•10 years ago
|
||
Seeing the STR go from ~450MB to ~1.3GB when loading that snapshot, but as soon as I close my tab or toolbox, it goes down pretty rapidly, even after trying a few times. I know it's unpredictable, but if the scenario can occur where it takes a few minutes, then maybe we should consider a flush when closing the toolbox. If you don't think that necessary, or a very edge case, then let's close this.
Flags: needinfo?(jsantell)
Comment 4•10 years ago
|
||
Since it appears to be going away on the next GC/CC cycle, I think we have nothing to worry about. If Firefox is memory constrained, it will trigger a cycle sooner. If it is not memory constrained, then having some unused memory floating for a little bit is no biggie.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
Updated•7 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•