766887 - Intermittent crash during test_HTMLLIElement01.html [@ js::GCMarker::processMarkStackOther]

Status: RESOLVED INVALID

(Core :: JavaScript Engine, defect)

Description

[Ed Morley [:emorley]]

Rev4 MacOSX Snow Leopard 10.6 mozilla-inbound opt test mochitests-3/5 on 2012-06-20 11:04:34 PDT for push 4ed14a1ce6c2

slave: talos-r4-snow-041

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

{
9763 INFO TEST-START | /tests/dom/tests/mochitest/dom-level2-html/test_HTMLLIElement01.html
TEST-UNEXPECTED-FAIL | /tests/dom/tests/mochitest/dom-level2-html/test_HTMLLIElement01.html | Exited with code 1 during test run
INFO | automation.py | Application ran for: 0:04:21.922834
INFO | automation.py | Reading PID log: /var/folders/Hs/HsDn6a9SG8idoIya6p9mtE+++TI/-Tmp-/tmplCI020pidlog
Downloading symbols from: http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-inbound-macosx64/1340213355/firefox-16.0a1.en-US.mac.crashreporter-symbols.zip
PROCESS-CRASH | /tests/dom/tests/mochitest/dom-level2-html/test_HTMLLIElement01.html | application crashed (minidump found)
Crash dump filename: /var/folders/Hs/HsDn6a9SG8idoIya6p9mtE+++TI/-Tmp-/tmp4HZ5xp/minidumps/0BF6EBA3-55F7-4EE0-9C4C-E78565748B09.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: 0xfc0b8

Thread 0 (crashed)
 0  XUL!js::GCMarker::processMarkStackOther [Heap.h : 677 + 0x0]
    rbx = 0x78766330   r12 = 0x05e7e188   r13 = 0x00000000   r14 = 0x78762550
    r15 = 0x05e7e188   rip = 0x0266ca2a   rsp = 0x5fbf9d40   rbp = 0x5fbf9dd0
    Found by: given as instruction pointer in context
 1  XUL!js::GCMarker::drainMarkStack [Marking.cpp : 1129 + 0xe]
    rbx = 0x78766330   r12 = 0x05e7e188   r13 = 0x78766330   r14 = 0x78768c80
    r15 = 0x05ec1560   rip = 0x0266d78a   rsp = 0x5fbf9de0   rbp = 0x5fbf9e40
    Found by: call frame info
 2  XUL!GCCycle [jsgc.cpp : 3629 + 0x1c]
    rbx = 0x59f6b638   r12 = 0x00000002   r13 = 0x00002710   r14 = 0x05e7e188
    r15 = 0x05e7e000   rip = 0x024c2cb6   rsp = 0x5fbf9e50   rbp = 0x5fbf9f20
    Found by: call frame info
 3  XUL!Collect [jsgc.cpp : 3886 + 0x10]
    rbx = 0x05e7e000   r12 = 0x05e7e258   r13 = 0x00000001   r14 = 0x00002710
    r15 = 0x00000000   rip = 0x024c3f67   rsp = 0x5fbf9f30   rbp = 0x5fbf9f70
    Found by: call frame info
 4  XUL!js::NotifyDidPaint [jsfriendapi.cpp : 749 + 0xe]
    rbx = 0x05e7e000   r12 = 0x2db6f3a0   r13 = 0x25e5d780   r14 = 0x00000003
    r15 = 0x08ee6bf8   rip = 0x024b66ae   rsp = 0x5fbf9f80   rbp = 0x5fbf9f90
    Found by: call frame info
 5  XUL!nsXPConnect::NotifyDidPaint [nsXPConnect.cpp : 2732 + 0xf]
    rbx = 0xffffffff   r12 = 0x2db6f3a0   r13 = 0x25e5d780   r14 = 0x00000003
    r15 = 0x08ee6bf8   rip = 0x01acee74   rsp = 0x5fbf9fa0   rbp = 0x5fbf9fa0
    Found by: call frame info
 6  XUL!PresShell::Paint [nsPresShell.cpp : 5195 + 0x8]
    rbx = 0xffffffff   r12 = 0x2db6f3a0   r13 = 0x25e5d780   r14 = 0x00000003
    r15 = 0x08ee6bf8   rip = 0x01246f33   rsp = 0x5fbf9fb0   rbp = 0x5fbfa0f0
    Found by: call frame info
 7  XUL!nsViewManager::Refresh [nsViewManager.cpp : 341 + 0x1c]
    rbx = 0x09804470   r12 = 0x5fbfa110   r13 = 0x5fbfa458   r14 = 0x09dfc980
    r15 = 0x00000000   rip = 0x0170f5a3   rsp = 0x5fbfa100   rbp = 0x5fbfa1a0
    Found by: call frame info
 8  XUL!nsViewManager::DispatchEvent [nsViewManager.cpp : 770 + 0x1e]
    rbx = 0x09dfc980   r12 = 0x09804470   r13 = 0x09dfc980   r14 = 0x5fbfa400
    r15 = 0x5fbfa2dc   rip = 0x017104cd   rsp = 0x5fbfa1b0   rbp = 0x5fbfa2b0
    Found by: call frame info
 9  XUL!HandleEvent [nsView.cpp : 127 + 0xf]
    rbx = 0x09dfc980   r12 = 0x5fbfa400   r13 = 0x5fbfa400   r14 = 0x5fbfa310
    r15 = 0x5fbfa36c   rip = 0x0170c3be   rsp = 0x5fbfa2c0   rbp = 0x5fbfa2f0
}

Comment 1

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

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.