lmac wrote:
XPConnect WrappedNative is being accessed on multiple threads but the underlying native xpcom object does not have a nsIClassInfo with the 'THREADSAFE' flag set wrapper: [xpconnect wrapped nsIEventQueueService @ 0x999be28 (native @ 0x8f77118)]
Probably a Mozilla bug... the event queue service ought to be marked as threadsafe, because it is.
However, as trunk doesn't have an event queue service anymore, that bug is unlikely to be fixed (trunk's thread manager is marked as threadsafe).
FWIW, that the Callback object in threaddemo is marked as threadsafe in the classinfo flags is a lie... it is not really threadsafe, being an object with a DOM global object.
-christian -- All the world's a stage, And all the men and women merely players: They have their exits and their entrances; And one man in his time plays many parts, [...] --W. Shakespeare _______________________________________________ dev-tech-xpcom mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-xpcom
