Closed Bug 54636 Opened 25 years ago Closed 23 years ago

nsRegistry is not threadsafe

Categories

(Core :: XPCOM, defect, P3)

Product:
Core
Component:
XPCOM
Type:
defect

Tracking

()

Status:
RESOLVED WONTFIX
Milestone:
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.
setting Jon Smirl's bugs to New
Status: UNCONFIRMED → NEW
Ever confirmed: true
Transferring to default XPCOM owner.
Assignee: rayw → warren
Blocks: 101976
again to default
Assignee: warren → dougt
QA Contact: rayw → dougt
Target Milestone: --- → mozilla1.1
moving out based on my workload. Yell, if you have a problem.
Keywords: helpwanted
Target Milestone: mozilla1.1alpha → Future
nsRegistry is no longer used by XPCOM (post 1.1). See bug 168584 on removing this class from xpcom completely.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WONTFIX
Component: XPCOM Registry → XPCOM
QA Contact: doug.turner → xpcom
You need to log in before you can comment on or make changes to this bug.