This is the issue from bug 863646, which is now closed, because we fixed the startup crash with a backout of bug 860438. But we still need to fix this.
I wonder if this is related to the shutdown leaks I see from running the profile manager.
Created attachment 740390 [details] [diff] [review] Force layout initialization in XPCOM initialization. r=bsmedberg This patch was r+-ed on the other bug.
Attachment #740390 - Flags: review+
Created attachment 740392 [details] [diff] [review] Fix standalone unit test to use the JSRuntime from XPConnect. v1 It turns out that the JS engine asserts that we only ever have one JSRuntime per thread. So when we spin up XPConnect in XPCOM initialization, we run into assertions when this standalone test does JS_NewRuntime. FWIW, it probably shouldn't be creating a random runtime and then passing that cx into Gecko APIs anyway. It sure would be nice if C++ unit tests could run with internal linkage... :-(
Attachment #740392 - Flags: review?(benjamin)
Comment on attachment 740392 [details] [diff] [review] Fix standalone unit test to use the JSRuntime from XPConnect. v1 You could just make this a gtest...
Attachment #740392 - Flags: review?(benjamin) → review+
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla23
You need to log in before you can comment on or make changes to this bug.