Here are the thread safe asserts that I'm hitting:
54633 nor P3 All [EMAIL PROTECTED] NEW nsCategoryManagerFactory is not
threadsafe
54635 nor P3 All [EMAIL PROTECTED] NEW nsRegistryFactory is not threadsafe
54636 nor P3 All [EMAIL PROTECTED] NEW nsRegistry is not threadsafe
54638 nor P3 All [EMAIL PROTECTED] NEW nsComponentManagerImpl is not
threadsafe
54639 nor P3 Oth [EMAIL PROTECTED] NEW nsCategoryManager is not
threadsafe
56706 nor P3 Oth [EMAIL PROTECTED] NEW bcORB not thread safe
56728 nor P3 All [EMAIL PROTECTED] NEW bcJavaComponentFactory not
thread-safe
56734 nor P3 All [EMAIL PROTECTED] NEW bcJavaStubsAndProxies not
thread-safe
56738 nor P3 All [EMAIL PROTECTED] NEW bcJavaComponentLoader not thread-safe
56740 nor P3 All [EMAIL PROTECTED] NEW bcXPCOMStubsAndProxies not
thread-safe
I'm using XPCOM from Apache under Windows. In this environment I can't
control control what tread calls InitXPCOM, termXPCOM or CreateInstance. As
a result of this I trip the thread safe assert all the time. The Java
asserts come form calling XPCOM components written in Java.
If you fix #54639 you'll just hit 54633, 54635, 54636, and 54638 . In in my
local code I have altered all of these asserts to the IMPL_THREADSAFE macro.
I occasionally get crashes from the lack of thread safety but at least it
lets me keep working on my app.
--
Jon Smirl
[EMAIL PROTECTED]
