Closed
Bug 768017
Opened 12 years ago
Closed 12 years ago
Intermittent crash in jsreftest.html?test=js1_5/Regress/regress-360969-05.js | Exited with code 1 during test run [@ XUL@0x2293320]
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: emorley, Unassigned)
References
Details
(Keywords: crash, intermittent-failure, Whiteboard: [js:t])
Crash Data
Rev4 MacOSX Snow Leopard 10.6 mozilla-inbound debug test jsreftest on 2012-06-24 13:38:01 PDT for push 85e7655b9ac0 slave: talos-r4-snow-041 https://tbpl.mozilla.org/php/getParsedLog.php?id=12956156&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 | 2059 / 3410 (60%) ++DOMWINDOW == 10 (0x126a05b90) [serial = 3908] [outer = 0x10a228300] BUGNUMBER: 360969 STATUS: 2^17: local function --DOMWINDOW == 9 (0x1419d9450) [serial = 3906] [outer = 0x10a228300] [url = file:///Users/cltbld/talos-slave/test/build/jsreftest/tests/jsreftest.html?test=js1_5/Regress/regress-360969-04.js] --DOMWINDOW == 8 (0x1281f83c0) [serial = 3903] [outer = 0x10a228300] [url = data:text/html,%3C%21%2D%2DCLEAR%2D%2D%3E] 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:07:41.851399 INFO | automation.py | Reading PID log: /var/folders/Hs/HsDn6a9SG8idoIya6p9mtE+++TI/-Tmp-/tmpQ6z6pLpidlog Downloading symbols from: http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-inbound-macosx64-debug/1340569483/firefox-16.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-/tmpJipPHm/minidumps/3C2608E5-1C2D-44CD-B0D3-0E110FA18230.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: 0x402a0000 Thread 0 (crashed) 0 XUL + 0x2293320 rbx = 0x2cad5570 r12 = 0x402a06c0 r13 = 0x2cba7000 r14 = 0x5fbfa850 r15 = 0x5fbfa858 rip = 0x03a93320 rsp = 0x5fbfa830 rbp = 0x5fbfa890 Found by: given as instruction pointer in context 1 XUL + 0x26f018f rip = 0x03ef0190 rsp = 0x5fbfa890 Found by: stack scanning 2 XUL + 0x22e54fd rip = 0x03ae54fe rsp = 0x5fbfa8a0 Found by: stack scanning 3 libSystem.B.dylib + 0x714c rip = 0x87ed914d rsp = 0x5fbfa8c0 Found by: stack scanning Thread 1 0 libSystem.B.dylib + 0x19c0a rbx = 0x000c3e50 r12 = 0x70f0f998 r13 = 0x70f0fd68 r14 = 0xffffffff r15 = 0x70f0fda8 rip = 0x87eebc0a rsp = 0x000c3ce8 rbp = 0x000c3e90 Found by: given as instruction pointer in context 1 libSystem.B.dylib + 0x1badc rip = 0x87eedadd rsp = 0x000c3cf0 Found by: stack scanning 2 libSystem.B.dylib + 0x1ca9a rip = 0x87eeea9b rsp = 0x000c3d50 Found by: stack scanning 3 libSystem.B.dylib + 0x1c92c rip = 0x87eee92d rsp = 0x000c3d70 Found by: stack scanning 4 libSystem.B.dylib + 0x1c78a rip = 0x87eee78b rsp = 0x000c3dc0 Found by: stack scanning 5 libSystem.B.dylib + 0x19c27 rip = 0x87eebc28 rsp = 0x000c3df0 Found by: stack scanning 6 libSystem.B.dylib + 0x1b795 rip = 0x87eed796 rsp = 0x000c3e10 Found by: stack scanning }
Updated•12 years ago
|
Whiteboard: [orange] → [js:t][orange]
Comment hidden (Legacy TBPL/Treeherder Robot) |
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
Updated•12 years ago
|
Keywords: intermittent-failure
Updated•12 years ago
|
Whiteboard: [js:t][orange] → [js:t]
You need to log in
before you can comment on or make changes to this bug.
Description
•