Remove original malloc memory accounting framework
Categories
(Core :: JavaScript: GC, task, P1)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox70 | --- | fixed |
People
(Reporter: jonco, Assigned: jonco)
References
Details
Attachments
(4 files)
Now that the more precise malloc tracking work has landed we should be able to remove the original framework.
| Assignee | ||
Comment 1•6 years ago
|
||
First of all remove the runtime-wide malloc bytes tracking. There's only a few uses of this so it almost never triggers a collection, and most of these uses are tracked in other ways anyway.
Depends on D39730
| Assignee | ||
Comment 2•6 years ago
|
||
Depends on D39731
| Assignee | ||
Comment 3•6 years ago
|
||
This replaces the original JIT code memory counter with one that tracks the allocated JIT code precisely. This now uses a fixed threshold which was the original intention.
This also removes the INCREMENTAL_MALLOC_TRIGGER GC reason and all GCs triggered by malloc allocations use TOO_MUCH_MALLOC, so whether a GC is incremental is separated from the trigger reason.
Depends on D39733
| Assignee | ||
Comment 4•6 years ago
|
||
Depends on D39734
Updated•6 years ago
|
Updated•6 years ago
|
Updated•6 years ago
|
Updated•6 years ago
|
Comment 6•6 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/c0cf078b5497
https://hg.mozilla.org/mozilla-central/rev/bda9fb62a8eb
https://hg.mozilla.org/mozilla-central/rev/86ec01cf8dac
https://hg.mozilla.org/mozilla-central/rev/694c0c845fd5
Description
•