Situation: - A js component that creates threads and executes code there - Chrome code that instantiates the component and calls a function on it, passing objects there - The component tries very carefully to stay away from DOM Stuff, especially global windows Starting in 1.7.7, that causes an extreme amount of assertions about lack of threadsafety of nsGlobalWindowImpl.
Created attachment 182896 [details] [diff] [review] possible patch? this patch avoids the assertions...
Created attachment 182898 [details] example of an assertion stack this is an example of the stack of this assertion (an nsDocument in this case... also happens with a window though)
Hopefully singlethreaded XPConnect means that this isn't an issue any more...
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.