Closed Bug 951285 Opened 9 years ago Closed 9 years ago

Assertion failure: js::CurrentThreadCanReadCompilationData(), at jsfun.h

Categories

(Core :: JavaScript Engine: JIT, defect)

x86_64
macOS
defect
Not set
critical

Tracking

()

VERIFIED FIXED
mozilla29

People

(Reporter: gkw, Assigned: bhackett1024)

References

Details

(Keywords: assertion, regression, testcase)

Attachments

(2 files)

Attached file lldb stack
function f(input) {
    for (var k = 0; k < 999; k++) {
        input();
    }
}
g = (function(x) {
    ff = x.ff;
    return (function() {
        ff()
    });
})({
    ff: (function() {
        'fa'.replace(/a/g, String.localeCompare)
    })
});
f(g);

asserts js debug shell on m-c changeset d58545aaeab9 with -D at Assertion failure: js::CurrentThreadCanReadCompilationData(), at jsfun.h

My configure flags are:

CC="clang -Qunused-arguments" AR=ar CXX="clang++ -Qunused-arguments" sh ./configure --target=x86_64-apple-darwin12.5.0 --enable-optimize --enable-debug --enable-profiling --enable-gczeal --enable-debug-symbols --enable-methodjit --enable-type-inference --disable-tests --with-ccache --enable-threadsafe <other NSPR options>

=== Tinderbox Build Bisection Results ===

Last "good" changeset has timestamp "20131216104657" and the hash "3df0585a23a1"
First "bad" changeset has timestamp "20131216105355" and the hash "dbeea0e93b56"

Likely regression window: http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=3df0585a23a1&tochange=dbeea0e93b56


Regression window only has bug 785905 in it. Brian, is it a likely regressor?
Flags: needinfo?(bhackett1024)
Attached patch patchSplinter Review
Assignee: nobody → bhackett1024
Attachment #8350365 - Flags: review?(jdemooij)
Flags: needinfo?(bhackett1024)
Attachment #8350365 - Flags: review?(jdemooij) → review+
https://hg.mozilla.org/mozilla-central/rev/07df5b26051d
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla29
Flags: in-testsuite?
Keywords: verifyme
Status: RESOLVED → VERIFIED
JSBugMon: This bug has been automatically verified fixed.
Keywords: verifyme
You need to log in before you can comment on or make changes to this bug.