Intermittent crash in js1_5/Regress/regress-360969-05.js [@ JSString::readBarrier]

RESOLVED INVALID

Status

()

Core
JavaScript Engine
--
critical
RESOLVED INVALID
6 years ago
6 years ago

People

(Reporter: emorley, Unassigned)

Tracking

({crash, intermittent-failure})

Trunk
x86_64
Mac OS X
crash, intermittent-failure
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(crash signature)

Rev4 MacOSX Snow Leopard 10.6 mozilla-inbound debug test jsreftest on 2012-08-08 05:11:33 PDT for push 4823b8b02b27

slave: talos-r4-snow-041

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

{
REFTEST TEST-START | file:///Users/cltbld/talos-slave/test/build/jsreftest/tests/jsreftest.html?test=js1_5/Regress/regress-360969-05.js | 2040 / 3213 (63%)
++DOMWINDOW == 10 (0x124b03d00) [serial = 3872] [outer = 0x1219a1780]
BUGNUMBER: 360969
STATUS: 2^17: local function
TEST-UNEXPECTED-FAIL | file:///Users/cltbld/talos-slave/test/build/jsreftest/tests/jsreftest.html?test=js1_5/Regress/regress-360969-05.js | Exited with code 1 during test run
INFO | automation.py | Application ran for: 0:08:14.443027
INFO | automation.py | Reading PID log: /var/folders/Hs/HsDn6a9SG8idoIya6p9mtE+++TI/-Tmp-/tmp0z7mV9pidlog
Downloading symbols from: http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-inbound-macosx64-debug/1344390747/firefox-17.0a1.en-US.mac64.crashreporter-symbols.zip
PROCESS-CRASH | file:///Users/cltbld/talos-slave/test/build/jsreftest/tests/jsreftest.html?test=js1_5/Regress/regress-360969-05.js | application crashed (minidump found)
Crash dump filename: /var/folders/Hs/HsDn6a9SG8idoIya6p9mtE+++TI/-Tmp-/tmpyeDsdd/minidumps/A32A8455-CB5D-4DC6-9CA4-1137C5F249BB.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: 0x2576d000

Thread 0 (crashed)
 0  XUL!JSString::readBarrier [Heap.h : 1010 + 0x0]
    rbx = 0x2576d680   r12 = 0x06861b60   r13 = 0x00000000   r14 = 0x06861268
    r15 = 0x223f2d20   rip = 0x03400208   rsp = 0x5fbf68d0   rbp = 0x5fbf68e0
    Found by: given as instruction pointer in context
 1  XUL!js::MarkAtomState [jsatominlines.h : 23 + 0x7]
    rip = 0x03413d52   rsp = 0x5fbf68f0
    Found by: stack scanning
 2  XUL!js::gc::Cell::isAligned [Heap.h : 1017 + 0x4]
    rip = 0x03644bde   rsp = 0x5fbf6900
    Found by: stack scanning
 3  XUL!js::MarkRuntime [jsgc.cpp : 2511 + 0x42]
    rip = 0x03458029   rsp = 0x5fbf6960
    Found by: stack scanning
 4  XUL!dosprintf [jsprf.cpp : 999 + 0x13]
    rip = 0x03503ece   rsp = 0x5fbf6980
    Found by: stack scanning
 5  libSystem.B.dylib + 0xa329
    rip = 0x87edc32a   rsp = 0x5fbf6990
    Found by: stack scanning
 6  libSystem.B.dylib + 0x714c
    rip = 0x87ed914d   rsp = 0x5fbf69c0
    Found by: stack scanning
}
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
Last Resolved: 6 years ago
Resolution: --- → INVALID
Keywords: intermittent-failure
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.