Re: How to create multiple contexts in different threads?
Jason Orendorff <[email protected]>
| Newsgroups | gmane.comp.mozilla.devel.jseng |
|---|---|
| Message-ID | <CA+W3DWEeEBv0V9kZSQMr0msP-19_YVPa6KbMSUUkADqeXB7KCw@mail.gmail.com> |
On Tue, Mar 29, 2016 at 4:16 AM, Clément Vuchener < [email protected]> wrote: > > OK. Does this happen when you call JS_NewRuntime, or later? Can you get a > > stack trace? > > It happens in JS_NewRuntime. There may actually be different assertion > depending on some race. > This is good information. I'm at a loss. If I were investigating this locally, I would start by printing the value of lockOwner and PR_GetCurrentThread() in the relevant places. The initial goal is to figure out if the bug is in SM or NSPR. (You can do this with GDB rather than messing with the code and recompiling, but I guess it's a bit of a pain either way.) How are you building SpiderMonkey and your app? Can you post the configure command line? Does configuring with --enable-posix-nspr-emulation make it go away? At this point, it could still be just about anything, but wild guesses include: - enabling exceptions in the app, and not in SpiderMonkey, might mess up the ABI somehow; - there could be some NSPR or SM header-vs-runtime version mismatch; - maybe DEBUG is #defined when compiling some SM source files but not others, perhaps due to a build system bug when building with unusual options -j _______________________________________________ dev-tech-js-engine mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine