Closed Bug 782501 Opened 12 years ago Closed 12 years ago

Intermittent crash [@ nsGenericElement::UnbindFromTree] in test_DOMImplementation-createDocument.html

Categories

(Core :: DOM: Core & HTML, defect)

x86_64
macOS
defect
Not set
critical

Tracking

()

RESOLVED INVALID

People

(Reporter: philor, Unassigned)

References

Details

(Keywords: crash, intermittent-failure, Whiteboard: [test which aborts the suite])

Crash Data

https://tbpl.mozilla.org/php/getParsedLog.php?id=14357420&tree=Mozilla-Inbound
Rev4 MacOSX Snow Leopard 10.6 mozilla-inbound opt test mochitests-2/5 on 2012-08-13 19:57:29 PDT for push 636c283ed0ed
slave: talos-r4-snow-013

7712 INFO TEST-PASS | /tests/dom/imptests/webapps/DOMCore/tests/submissions/Ms2ger/test_DOMImplementation-createDocument.html | Finished test, status 0
TEST-UNEXPECTED-FAIL | /tests/dom/imptests/webapps/DOMCore/tests/submissions/Ms2ger/test_DOMImplementation-createDocument.html | Exited with code 1 during test run
INFO | automation.py | Application ran for: 0:05:27.295372
INFO | automation.py | Reading PID log: /var/folders/Hs/HsDn6a9SG8idoIya6p9mtE+++TI/-Tmp-/tmpMWrREcpidlog
Downloading symbols from: http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-inbound-macosx64/1344909342/firefox-17.0a1.en-US.mac.crashreporter-symbols.zip
PROCESS-CRASH | /tests/dom/imptests/webapps/DOMCore/tests/submissions/Ms2ger/test_DOMImplementation-createDocument.html | application crashed (minidump found)
Crash dump filename: /var/folders/Hs/HsDn6a9SG8idoIya6p9mtE+++TI/-Tmp-/tmpnci0Xg/minidumps/4A2F879E-2562-44F5-B998-EEB5EA105161.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: 0x4c6026f8

Thread 0 (crashed)
 0  XUL!nsGenericElement::UnbindFromTree [nsGenericElement.cpp : 1541 + 0x0]
    rbx = 0x00000001   r12 = 0x00000001   r13 = 0x800a4e80   r14 = 0x800a4e80
    r15 = 0x00000000   rip = 0x014207ce   rsp = 0x5fbfcd50   rbp = 0x5fbfcdc0
    Found by: given as instruction pointer in context
 1  XUL!nsNodeUtils::LastRelease [nsNodeUtils.cpp : 251 + 0xb]
    rip = 0x014342b7   rsp = 0x5fbfcd70
    Found by: stack scanning
 2  XUL!nsGenericDOMDataNode::UnbindFromTree [nsGenericDOMDataNode.cpp : 536 + 0x5]
    rip = 0x0141d1af   rsp = 0x5fbfcd80
    Found by: stack scanning
 3  XUL!nsGenericHTMLElement::UnbindFromTree [nsGenericHTMLElement.cpp : 1768 + 0xe]
    rip = 0x0150e988   rsp = 0x5fbfcdd0
    Found by: stack scanning
 4  XUL!ContentUnbinder::UnbindSubtree [FragmentOrElement.cpp : 1161 + 0x15]
    rip = 0x0147322c   rsp = 0x5fbfce10
    Found by: stack scanning
 5  XUL!ContentUnbinder::UnbindSubtree [FragmentOrElement.cpp : 1160 + 0xa]
    rip = 0x01473216   rsp = 0x5fbfce50
    Found by: stack scanning
 6  XUL!ContentUnbinder::Run [FragmentOrElement.cpp : 1173 + 0x7]
    rip = 0x01472fc1   rsp = 0x5fbfce90
    Found by: stack scanning
 7  XUL!nsThread::ProcessNextEvent [nsThread.cpp : 624 + 0x5]
    rip = 0x01f4508d   rsp = 0x5fbfced0
    Found by: stack scanning
Crash Signature: [@ nsGenericElement::UnbindFromTree]
Keywords: crash
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][test which aborts the suite] → [test which aborts the suite]
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.