767817 - Assertion failure: compartment mismatched | Assertion failure: false (compartment mismatched)

Status: RESOLVED WORKSFORME

(Core :: JavaScript Engine, defect)

Description

[Bob Clary [:bc] (inactive)]

1. http://www.canalplus.fr/c-divertissement/pid1782-c-sav-des-emissions.html?vid=673186

or http://www.canalplus.fr/c-divertissement/pid1784-c-les-guignols.html

or http://www.touran-fahren.de/forum/viewtopic.php?f=209&t=1965&view=unread#unread 

2. Shutdown

3.
Assertion failure: compartment mismatched, at c:\work\mozilla\builds\beta\mozilla\js\src\jscntxtinlines.h:156

Assertion failure: compartment mismatched, at c:\work\mozilla\builds\aurora\mozilla\js\src\jscntxtinlines.h:237

Assertion failure: false (compartment mismatched), at c:\work\mozilla\builds\nightly\mozilla\js\src\jscntxtinlines.h:242

I see this on Beta (once in automation), Aurora and Nighlty. It appears to be most reliable on Windows 64bit with 32bit builds and OS X 10.7 but occurs on Windows XP, Windows 7, Linux and OS X.

You may need to load the url and shutdown several times to see the assertion.

ss since there are other compartment related assertions which are ss.

bug 720714
bug 723068
bug 731549
bug 765416
bug 763225

Comment 1

[David Bolter [:davidb] (NeedInfo me for attention)]

Naveed agreed to own this for triage.

Comment 2

[Andrew McCreight [:mccr8]]

Does this still reproduce in a debug build? What does the stack look like?

Comment 3

[Bob Clary [:bc] (inactive)]

I haven't been able to reproduce the original assertion after repeated attempts either with recent builds on all three branches or with builds from changesets when this was originally filed. I did find a different assertion failure: state.numThreads but that was fixed in December. I'll call this works for me. Is there any reason to keep this s-s?