Closed
Bug 780571
Opened 12 years ago
Closed 12 years ago
Intermittent crash in js1_5/Regress/regress-416628.js [@ XUL@0x1e4db62]
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: emorley, Unassigned)
References
Details
(Keywords: crash, intermittent-failure)
Crash Data
Rev4 MacOSX Snow Leopard 10.6 mozilla-central debug test jsreftest on 2012-08-05 08:46:18 PDT for push 6347710412a5 slave: talos-r4-snow-041 https://tbpl.mozilla.org/php/getParsedLog.php?id=14144711&tree=Firefox { REFTEST TEST-START | file:///Users/cltbld/talos-slave/test/build/jsreftest/tests/jsreftest.html?test=js1_5/Regress/regress-416628.js | 1862 / 3213 (57%) ++DOMWINDOW == 10 (0x128dad660) [serial = 3516] [outer = 0x1001f9c80] BUGNUMBER: 416628 STATUS: O(n^2) blowup due to overlong cx->tempPool arena list --DOMWINDOW == 9 (0x1264c1f60) [serial = 3514] [outer = 0x1001f9c80] [url = file:///Users/cltbld/talos-slave/test/build/jsreftest/tests/jsreftest.html?test=js1_5/Regress/regress-347306-01.js] --DOMWINDOW == 8 (0x1270e6a30) [serial = 3511] [outer = 0x1001f9c80] [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-416628.js | Exited with code 1 during test run INFO | automation.py | Application ran for: 0:07:10.883069 INFO | automation.py | Reading PID log: /var/folders/Hs/HsDn6a9SG8idoIya6p9mtE+++TI/-Tmp-/tmp4X9t3Dpidlog Downloading symbols from: http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-central-macosx64-debug/1344180687/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-416628.js | application crashed (minidump found) Crash dump filename: /var/folders/Hs/HsDn6a9SG8idoIya6p9mtE+++TI/-Tmp-/tmpEZBZeC/minidumps/CF4458B5-B852-4668-9CB1-88C11FEFD029.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: 0x27afcf08 Thread 0 (crashed) 0 XUL + 0x1e4db62 rbx = 0x25bd9c00 r12 = 0x00000000 r13 = 0x00000000 r14 = 0x27a39538 r15 = 0x27afc0b8 rip = 0x0364db62 rsp = 0x5fbf6730 rbp = 0x5fbf6760 Found by: given as instruction pointer in context 1 XUL + 0x1e4a85b rip = 0x0364a85c rsp = 0x5fbf6770 Found by: stack scanning 2 XUL + 0x1e4dfab rip = 0x0364dfac rsp = 0x5fbf67a0 Found by: stack scanning 3 XUL + 0x1e49dce rip = 0x03649dcf rsp = 0x5fbf67f0 Found by: stack scanning 4 XUL + 0x1c67cd7 rip = 0x03467cd8 rsp = 0x5fbf6820 Found by: stack scanning 5 libSystem.B.dylib + 0x714c rip = 0x87ed914d rsp = 0x5fbf6830 Found by: stack scanning 6 XUL + 0x1ea5a95 rip = 0x036a5a96 rsp = 0x5fbf6870 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
Closed: 12 years ago
Resolution: --- → INVALID
Updated•12 years ago
|
Keywords: intermittent-failure
Updated•12 years ago
|
Whiteboard: [orange]
You need to log in
before you can comment on or make changes to this bug.
Description
•