Changes to mozjemalloc's committed memory calculation
Categories
(Core :: Memory Allocator, task)
Tracking
()
Tracking | Status | |
---|---|---|
firefox121 | --- | fixed |
People
(Reporter: pbone, Assigned: pbone)
References
Details
Attachments
(3 files, 1 obsolete file)
As I was working on Bug 1857841 I kept hitting assertions with the amount of committed memory. So I added more assertions to catch problems sooner and made other changes to committed memory to make sure it was correct.
Assignee | ||
Comment 1•1 year ago
|
||
Assignee | ||
Comment 2•1 year ago
|
||
I wrote this to help me with debugging. I was finding that the committed
memory would end up larger than the mapped memory when jemalloc_stats() was
called. To figure out why I added this counter to each chunk and check that
it remains in bounds and that when we dispose the chunk that it returns to
0.
It's only build when MOZ_DEBUG is defined
Depends on D192447
Assignee | ||
Comment 3•1 year ago
|
||
The waste memory calcuation has an invariant that we can also assert.
Depends on D192448
Assignee | ||
Comment 4•1 year ago
|
||
Don't include the chunk guard pages in our committed memory calculation.
Depends on D192449
Updated•1 year ago
|
Updated•1 year ago
|
Comment 6•1 year ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/a34246d067fa
https://hg.mozilla.org/mozilla-central/rev/d41876c49d2d
https://hg.mozilla.org/mozilla-central/rev/81c46dfe35a0
Description
•