Closed
Bug 1683410
Opened 3 years ago
Closed 3 years ago
nsThreadManager's thread shutdown check should be atomic
Categories
(Core :: XPCOM, task)
Core
XPCOM
Tracking
()
RESOLVED
FIXED
86 Branch
Tracking | Status | |
---|---|---|
firefox86 | --- | fixed |
People
(Reporter: KrisWright, Assigned: KrisWright)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
This is accessed offthread when threads are destroyed and set when nsThreadManager
shuts down, and as noted by tsan it's capable of racing. The easiest fix is to just make sShutdownComplete atomic.
Assignee | ||
Comment 1•3 years ago
|
||
This is changed on the main thread by nsThreadManager
and should probably just be made atomic.
Updated•3 years ago
|
Assignee: nobody → kwright
Status: NEW → ASSIGNED
Comment 2•3 years ago
|
||
Also filed Bug 1683407 for this
Pushed by kwright@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/ee1e88f47db9 Make sShutdownComplete atomic r=xpcom-reviewers,mccr8
Comment 4•3 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
status-firefox86:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 86 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•