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 03:45 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)? If > so, you must define JS_THREADSAFE (even if you use a runtime per thread). If the JS engine doesn't use any global or static variables, and a separate runtime is used per thread, why would there be any "thread safety" issues? Sorry for questioning your answer, but I just don't understand what necessitates the requirement. :-) If a separate runtime is used per thread, no JS_BeginRequest/EndRequest calls are required though, correct? -Rob .