Closed
Bug 1776833
Opened 3 years ago
Closed 3 years ago
GC tunables require a lock to access even though that are only accessed on the main thread
Categories
(Core :: JavaScript: GC, task, P3)
Core
JavaScript: GC
Tracking
()
RESOLVED
FIXED
104 Branch
Tracking | Status | |
---|---|---|
firefox104 | --- | fixed |
People
(Reporter: jonco, Assigned: jonco)
References
Details
Attachments
(2 files)
This has been true since we removed off-thread allocation.
The one exception to to this is the settings for min/max number of free chunks, which is used by background allocation.
This is a tidyup as a prelude to bug 1770768.
Assignee | ||
Comment 1•3 years ago
|
||
The chunk settings move to GCRuntime where they are made GCLockData.
Almost all tunable settings become MainThreadData with the exception of
mallocThresholdBase which is accessed off-thread during sweeping since resizing
contains can cause allocation.
Assignee | ||
Comment 2•3 years ago
|
||
Depends on D150458
Pushed by jcoppeard@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/416f094f92a1
Part 1: Make GC tunables MainThreadData or move them to GCRuntime r=sfink
https://hg.mozilla.org/integration/autoland/rev/b8740c0dade3
Part 2: Remove use of GC lock when accessing GC tunables r=sfink
Comment 4•3 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/416f094f92a1
https://hg.mozilla.org/mozilla-central/rev/b8740c0dade3
Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox104:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 104 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•