the constructor and desstructor of nsAtomTable are not thread safe. see:
All of the NS_NewAtom methods need to be threadsafe too, not just the
creation/destruction of the hashtable that those methods use.
as with 12755, awaiting CoClasses, I think
mass re-assigning to my new bugzilla account
dp is no longer @netscape.com. changing qa contact to default for this product
dup of bug 12755, it seems. scc, please mark dup?
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.
*** This bug has been marked as a duplicate of 12755 ***