Closed Bug 12914 Opened 25 years ago Closed 23 years ago

nsAtomTable is not thread safe

Categories

(Core :: XPCOM, defect, P2)

Product:
Core
Component:
XPCOM
Platform:
x86
Windows NT
Type:
defect

Tracking

()

Status:
VERIFIED DUPLICATE of bug 12755
Milestone:
Future

People

(Reporter: dougt, Assigned: kandrot)

References

Details

the constructor and desstructor of nsAtomTable are not thread safe.  see:
http://bugzilla.mozilla.org/show_bug.cgi?id=12755
All of the NS_NewAtom methods need to be threadsafe too, not just the
creation/destruction of the hashtable that those methods use.
Status: NEW → ASSIGNED
Blocks: 12755
Target Milestone: M16
as with 12755, awaiting CoClasses, I think
Priority: P3 → P2
Target Milestone: M16 → Future
mass re-assigning to my new bugzilla account
Assignee: scc → scc
Status: ASSIGNED → NEW
Status: NEW → ASSIGNED
dp is no longer @netscape.com. changing qa contact to default for this product
QA Contact: dp → kandrot
dup of bug 12755, it seems.  scc, please mark dup?

/be
another threads bug.  I hate to dump on you, but I'll be focusing on strings.
If you don't want to take threading, we can discuss it at tomorrows XPCOM bug
meeting and figure out what to do.
Assignee: scc → kandrot
Status: ASSIGNED → NEW
Status: NEW → ASSIGNED
QA Contact: kandrot → scc

*** This bug has been marked as a duplicate of 12755 ***
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
v
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.