Closed Bug 781813 Opened 12 years ago Closed 12 years ago

Intermittent crash in jsreftest.html?test=e4x/XML/regress-324422-1.js [@ XUL@0x2244747 | js_TraceXML] ("Assertion failure: thing->compartment(), at ../../../js/src/jsgcmark.cpp:80")

Categories

(Core :: JavaScript Engine, defect)

14 Branch
x86_64
macOS
defect
Not set
critical

Tracking

()

RESOLVED INVALID

People

(Reporter: emorley, Unassigned)

References

Details

(Keywords: crash, intermittent-failure)

Crash Data

Rev4 MacOSX Snow Leopard 10.6 mozilla-aurora debug test jsreftest on 2012-05-29 18:41:50 PDT for push de4a9e14237e

slave: talos-r4-snow-013

https://tbpl.mozilla.org/php/getParsedLog.php?id=12177660&tree=Mozilla-Aurora

{
REFTEST TEST-START | file:///Users/cltbld/talos-slave/test/build/jsreftest/tests/jsreftest.html?test=e4x/XML/regress-324422-1.js | 244 / 3406 (7%)
++DOMWINDOW == 88 (0x12862f838) [serial = 440] [outer = 0x107db18c0]
BUGNUMBER: 324422
STATUS: Do not crash creating XML object with long initialiser
--- NOTE: IN THIS TESTCASE, WE EXPECT EXIT CODE 0 ---
--- NOTE: IN THIS TESTCASE, WE EXPECT EXIT CODE 5 ---
STATUS: 10485760
Assertion failure: thing->compartment(), at ../../../js/src/jsgcmark.cpp:80
TEST-UNEXPECTED-FAIL | file:///Users/cltbld/talos-slave/test/build/jsreftest/tests/jsreftest.html?test=e4x/XML/regress-324422-1.js | Exited with code 1 during test run
INFO | automation.py | Application ran for: 0:01:06.511732
INFO | automation.py | Reading PID log: /var/folders/Hs/HsDn6a9SG8idoIya6p9mtE+++TI/-Tmp-/tmpniNgm8pidlog
Downloading symbols from: http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-aurora-macosx64-debug/1338341273/firefox-14.0a2.en-US.mac64.crashreporter-symbols.zip
PROCESS-CRASH | file:///Users/cltbld/talos-slave/test/build/jsreftest/tests/jsreftest.html?test=e4x/XML/regress-324422-1.js | application crashed (minidump found)
Crash dump filename: /var/folders/Hs/HsDn6a9SG8idoIya6p9mtE+++TI/-Tmp-/tmpWFxr6v/minidumps/A24771D7-52C7-47F4-AB2F-15566FAB3674.dmp
Operating system: Mac OS X
                  10.6.8 10K549
CPU: amd64
     family 6 model 23 stepping 10
     2 CPUs

Crash reason:  EXC_BAD_ACCESS / KERN_INVALID_ADDRESS
Crash address: 0x0

Thread 0 (crashed)
 0  XUL + 0x2244747
    rbx = 0x89df3ec0   r12 = 0x06cb4228   r13 = 0x085b2ec0   r14 = 0x085b2000
    r15 = 0x89df3ed0   rip = 0x03a44747   rsp = 0x5fbfb6b0   rbp = 0x5fbfb700
    Found by: given as instruction pointer in context
 1  XUL!js_TraceXML [jsxml.cpp : 7331 + 0x13]
    rip = 0x03bbcaf4   rsp = 0x5fbfb710
    Found by: stack scanning
 2  XUL!js::GCMarker::processMarkStackOther [jsgcmark.cpp : 821 + 0xa]
    rip = 0x03a3c850   rsp = 0x5fbfb740
    Found by: stack scanning
 3  libSystem.B.dylib + 0x414e
    rip = 0x8579114f   rsp = 0x5fbfb780
    Found by: stack scanning
 4  XUL!js::GCMarker::drainMarkStack [jsgcmark.cpp : 1131 + 0xa]
    rip = 0x03a3d25b   rsp = 0x5fbfb7c0
    Found by: stack scanning
 5  XUL!GCCycle [jsgc.cpp : 3249 + 0x12]
    rip = 0x03a27b6e   rsp = 0x5fbfb7f0
    Found by: stack scanning
 6  libSystem.B.dylib + 0x414e
    rip = 0x8579114f   rsp = 0x5fbfb840
    Found by: stack scanning
 7  XUL!PRMJ_Now [prmjtime.cpp : 305 + 0x0]
    rip = 0x03bdde01   rsp = 0x5fbfb870
    Found by: stack scanning
 8  0x106cb3fff
    rip = 0x06cb4000   rsp = 0x5fbfb878
    Found by: call frame info
 9  XUL!js::gcstats::Statistics::endPhase [Statistics.cpp : 574 + 0x4]
    rip = 0x03cc3c9e   rsp = 0x5fbfb890
    Found by: stack scanning
10  XUL!Collect [jsgc.cpp : 3692 + 0x11]
    rip = 0x03a288ae   rsp = 0x5fbfb8e0
    Found by: stack scanning
11  XUL!js_InvokeOperationCallback [jscntxt.cpp : 870 + 0x11]
    rip = 0x039c67a2   rsp = 0x5fbfb950
    Found by: stack scanning
12  XUL!js_HandleExecutionInterrupt [jscntxt.cpp : 886 + 0x4]
    rip = 0x039c67c7   rsp = 0x5fbfb980
}
This bug was observed only on one or more of the six machines listed in
bug 787281 comment 11, which seem likely to have bad memory, disk, or
other hardware problem, based on the rate of failures on those machines
and the types of failures observed.

Therefore I'm marking this bug invalid, though it should be reopened if
it occurs on other (more reliable) hardware.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.