Closed
Bug 1637453
Opened 5 years ago
Closed 2 years ago
Ensure AbstractThread TLS is cleared when last reference to AbstractThread drops
Categories
(Core :: XPCOM, defect)
Core
XPCOM
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: jya, Unassigned)
References
(Blocks 1 open bug)
Details
There's potential for a use case that could lead to AbstractThread::GetCurrent() returning a dangling pointer.
We have to clear the AbstractThread TLS when the last reference is dropped.
Reporter | ||
Updated•5 years ago
|
Comment 1•2 years ago
|
||
We appear to correctly clear these flags when AbstractThread
is created and destroyed these days (XPCOMThreadWrapper, TaskQueue), and AbstractThread is generally going away, so I don't think this issue is relevant anymore.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•