Open
Bug 1873235
Opened 6 months ago
Updated 2 months ago
Leaking page repeatedly triggers GC without freeing any memory
Categories
(Core :: JavaScript: GC, enhancement, P2)
Core
JavaScript: GC
Tracking
()
NEW
People
(Reporter: jonco, Unassigned)
References
(Blocks 3 open bugs)
Details
(Keywords: perf:resource-use)
Pages that allocate memory up to the heap limit can enter a state where GC happens repeatedly without freeing up any memory. One example is bug 1867074 where this is caused by a leak.
Bug 1505622 was a previous attempt to fix problems like this.
|
||
Updated•6 months ago
|
Severity: -- → N/A
Priority: -- → P2
|
||
Updated•5 months ago
|
Blocks: power-usage
Keywords: perf:resource-use
|
||
Comment 1•4 months ago
|
||
bug 1853495 has a testcase/STR that should repro this (based on :joncos comment : https://bugzilla.mozilla.org/show_bug.cgi?id=1875304#c3)
|
|
||
Comment 2•2 months ago
|
||
Here is a profile I got recently: https://share.firefox.dev/3xCwn18
The content process includes the tab for chat.mozilla.org, and it likely leaks memory overtime (my browser session has lasted about a month and a half).
You need to log in
before you can comment on or make changes to this bug.
Description
•