Closed
Bug 54636
Opened 24 years ago
Closed 22 years ago
nsRegistry is not threadsafe
Categories
(Core :: XPCOM, defect, P3)
Core
XPCOM
Tracking
()
RESOLVED
WONTFIX
Future
People
(Reporter: jonsmirl, Assigned: dougt)
References
Details
(Keywords: helpwanted)
XPConnect standalone is a multithreaded environment. It should be legal to call CreateInstance from any thread. CreateInstance uses nsRegistry and triggers the non-thread safe assert when called from a non-primary thread. NS_IMPL_ISUPPORTS1( nsRegistry, nsIRegistry) Even if the decision is to serialize CreateInstance it still needs to be callable from any thread. This component needs to be checked for thread safety and switched to the THREADSAFE ISUPPORTS macro after any problems are fixed.
Comment 1•24 years ago
|
||
setting Jon Smirl's bugs to New
Status: UNCONFIRMED → NEW
Ever confirmed: true
Assignee | ||
Comment 3•23 years ago
|
||
again to default
Assignee: warren → dougt
QA Contact: rayw → dougt
Target Milestone: --- → mozilla1.1
Assignee | ||
Comment 4•22 years ago
|
||
moving out based on my workload. Yell, if you have a problem.
Keywords: helpwanted
Target Milestone: mozilla1.1alpha → Future
Assignee | ||
Comment 5•22 years ago
|
||
nsRegistry is no longer used by XPCOM (post 1.1). See bug 168584 on removing this class from xpcom completely.
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•