Closed
Bug 2062958
Opened 3 months ago
Closed 3 months ago
Clear mark bits for stolen chunks immediately if possible
Categories
(Core :: JavaScript: GC, task, P3)
Core
JavaScript: GC
Tracking
()
RESOLVED
FIXED
156 Branch
| Tracking | Status | |
|---|---|---|
| firefox156 | --- | fixed |
People
(Reporter: jonco, Assigned: jonco)
References
(Blocks 1 open bug)
Details
Attachments
(1 external file)
Following on from bug 2045637, we can clear the mark bits in stolen chunks immediately outside concurrent marking builds. This is more efficient since we don't have to iterate all the chunk lists later on.
For concurrent marking builds we can perhaps optimise this later.
| Assignee | ||
Comment 1•3 months ago
|
||
As per the comments we only need to defer clearing the mark bits in stolen
chunks if concurrent marking can be happening. It's best to avoid this if
possible because it means we need to iterate all the chunks.
Pushed by jcoppeard@mozilla.com:
https://github.com/mozilla-firefox/firefox/commit/ffe404accb90
https://hg.mozilla.org/integration/autoland/rev/d576a10c3c11
Clear mark bits in stolen chunks immediately outside concurrent marking builds r=sfink
Comment 3•3 months ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 3 months ago
status-firefox156:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 156 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•