Closed Bug 54639 Opened 24 years ago Closed 21 years ago

nsCategoryManager is not threadsafe

Categories

(Core :: XPCOM, defect, P3)

Product:
Core
Component:
XPCOM
Platform:
Other
Other
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla1.5alpha

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  nsCategoryManager 
and triggers the non-thread safe assert when called from the non-primary 
thread. NS_IMPL_ISUPPORTS1(nsCategoryManager, nsICategoryManager) 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
Summary: nsCategoryManager is not threadsafe → nsCategoryManager is not threadsafe
Blocks: 101976
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
Target Milestone: Future → mozilla1.4alpha
this is not immediately needed by any client that I am aware of.

alec, if you get to the category manager hash table clean up before me, we
should address this bug at the same time.
Target Milestone: mozilla1.4alpha → Future
Patch is in bug 193031
Fixed with my patch on bug 193031.
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Target Milestone: Future → mozilla1.5alpha
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.