Subj : Re: Access violation in JavaScript-C 1.5 pre-release 5 2003-01-10 for Win32 To : netscape.public.mozilla.jseng From : "Rob Swindell" Date : Tue May 06 2003 01:51 pm "Brendan Eich" wrote in message news:3EB7DB18.1090006@meer.net... > > >Does this assertion appear related to the access violation in > >JS_HashTableRawLookup or are they two unrelated anomolies? Sorry I'm not > >familiar with the inner-workings of the Spidermonkey GC engine. :-( > > > > > > Not clear. It would help to know more about your embedding. Do you use > multiple threads that might call into the JS API (it appears so from > your stack backtrace, but maybe only one thread uses the JS API)? Multiple threads use the JS API, but each thread has its own runtime and context. > If so, you must define JS_THREADSAFE (even if you use a runtime per thread). Really? I didn't want the bagage of the NSPR if I could help it. :-( I was under the impression that all the thread-sensitive data was contained in the runtime object and that if each thread used its own runtime there would be no collisions. > Have you tried running under purify or a similar tool? No, I have not. But if JS_THREADSAFE is truely required, then that is most likely the cause. Thanks again for the clarification, -Rob .