Open
Bug 1579796
Opened 5 years ago
Updated 4 years ago
Garbage builds up when running JS reftests
Categories
(Core :: JavaScript: GC, defect, P2)
Core
JavaScript: GC
Tracking
()
NEW
People
(Reporter: jonco, Unassigned)
Details
Continuing from bug 1518138. We use windowUtils.runNextCollectorTimer to run more aggressive collections during reftests to stop garbage building up and causing us to run out of memory. We should figure out why this is happening and fix it (and remove this hack).
|
Reporter | |
Comment 1•5 years ago
|
||
I've continued to look into this and my current theory is that we're not cycle collecting enough. Without calling windowUtils.runNextCollectorTimer the number of live DOM windows builds up and can pass 200 (!). GC is running regularly but sees most globals as live and so can't collect them.
|
|
Reporter | |
Updated•4 years ago
|
Severity: normal → S4
You need to log in
before you can comment on or make changes to this bug.
Description
•