Closed
Bug 717498
Opened 14 years ago
Closed 14 years ago
nsThread::mEventObservers doesn't get cleared at thread shutdown
Categories
(Core :: XPCOM, defect)
Core
XPCOM
Tracking
()
RESOLVED
FIXED
mozilla12
People
(Reporter: bholley, Assigned: bholley)
References
Details
Attachments
(1 file, 1 obsolete file)
2.29 KB,
patch
|
benjamin
:
review+
|
Details | Diff | Splinter Review |
Once the thread manager shuts down, calls to NS_GetCurrentThread return null. So any consumers with registered observers (such as nsXPConnect) have no way to unregister themselves if their shutdown happens after ThreadManager shutdown. This can lead to cycles.
Ideally we'd unify the whole SetObserver vs AddObserver setup, but that's a task for another day.
Assignee | ||
Comment 1•14 years ago
|
||
Attaching a patch. Flagging bsmedberg for review.
Attachment #587920 -
Flags: review?(benjamin)
Assignee | ||
Comment 2•14 years ago
|
||
Err, that patch had slightly erroneous context due to its location in my patch stack. Here's a version rebased to mozilla-central.
Attachment #587920 -
Attachment is obsolete: true
Attachment #587920 -
Flags: review?(benjamin)
Attachment #587921 -
Flags: review?(benjamin)
Updated•14 years ago
|
Attachment #587921 -
Flags: review?(benjamin) → review+
Assignee | ||
Comment 3•14 years ago
|
||
Assignee: nobody → bobbyholley+bmo
Target Milestone: --- → mozilla12
Comment 4•14 years ago
|
||
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•