Closed
Bug 1931799
Opened 11 months ago
Closed 11 months ago
don't bother tracking invidual frees if the displaylist and it's arena is doomed
Categories
(Core :: Web Painting, enhancement)
Core
Web Painting
Tracking
()
RESOLVED
FIXED
135 Branch
| Tracking | Status | |
|---|---|---|
| firefox135 | --- | fixed |
People
(Reporter: tnikkel, Assigned: tnikkel)
References
(Blocks 1 open bug)
Details
(Whiteboard: [sp3])
Attachments
(1 file)
No description provided.
| Assignee | ||
Comment 1•11 months ago
|
||
If the arena is going to go away we don't need to free each allocation, all that does is append it to a free list, which takes time, and then we'll have to destroy that free list too. The arena will de-allocate the memory the same.
This mirrors what we do for frames which also use the same arena (nsPresArena):
https://searchfox.org/mozilla-central/rev/f8488adfb9c3e25a80ba6a21e04950d58165e956/layout/base/PresShell.h#291
This does mean that we don't write the nsPresArena poison over the memory before we release it back to the OS (we are left with whatever zero-ing or poisoning is done or not done by the allocator at a lower level then nsPresArena).
Pushed by tnikkel@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/3e38c8e1415d
If the display list builder (and hence it's arena) is doomed we don't need to bother tracking freeing individual items to the arena. r=gfx-reviewers,nical$layout-reviewers
Status: NEW → RESOLVED
Closed: 11 months ago
status-firefox135:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 135 Branch
Updated•10 months ago
|
Whiteboard: [sp3]
Updated•10 months ago
|
See Also: → https://mozilla-hub.atlassian.net/browse/SP3-888
You need to log in
before you can comment on or make changes to this bug.
Description
•