I'm pretty sure that the bug or lack of understanding is mine, as I get this error message every time I access the JS Components variable. I have checked it and, no suprise, it is thread safe.
when I execute the same code a simple function call instead of creating a thread everything works fine, it is only the threaded version which has problems. At the last days I have learned that I need to create an event queue and event loop in order to have a working non trivial thread, can it be that there are some essential things which has to be done in the thread in order to execute code over xpconnect ?. Thanks, Mark. "Doug Turner" <[EMAIL PROTECTED]> wrote in message news:apigt4$fv31@;ripley.netscape.com... > The error indicates that whatever object you are trying to use via > javascript doesn't have the right flag set. Can you figure out which > interface or class you are using when this happens? Is it a class that > is part of mozilla, or is it your component? > > If it is the former, file a bug in bugzilla. If not, you should do what > the error suggests: ensure that your class implementation is threadsafe > and set the correct flag for your nsIClassInfo implementation. > > Doug Turner > [EMAIL PROTECTED] > > mark kaplun wrote: > > Hi, > > > > Can anyone explain to me the cuase for the following console message > > > > !!!!! XPConnect wrapper thread use error... > > XPConnect WrappedNative is being accessed on multiple threads but the > > underlying native xpcom object does not have a nsIClassInfo with the > > 'THREADSAFE' flag set > > > > I'm having a thread listening to network messages, which suppose to open > > an alert window, by using an XPCOM object implemented in JS. > > > > Any clue will be appriciated, > > > > Mark. > > > > >
