760056 - Intermittent tprow crash on www.guardian.co.uk/index.html [@ mozilla::places::History::UnregisterVisitedCallback]

Status: RESOLVED INVALID

(Toolkit :: Places, defect)

Description

[Ed Morley [:emorley]]

Rev4 MacOSX Snow Leopard 10.6 mozilla-central talos tprow on 2012-05-30 11:53:56 PDT for push 4c68e77d89d8

slave: talos-r4-snow-013

https://tbpl.mozilla.org/php/getParsedLog.php?id=12204919&tree=Firefox

{
NOISE: Cycle 1(3): loaded http://localhost/page_load_test/tp5/bild.de/www.bild.de/index.html (next: http://localhost/page_load_test/tp5/guardian.co.uk/www.guardian.co.uk/index.html)
NOISE: 
NOISE: __FAILbrowser non-zero return code (256)__FAIL
NOISE: Found crashdump: /var/folders/Hs/HsDn6a9SG8idoIya6p9mtE+++TI/-Tmp-/tmpoBEmxA/profile/minidumps/0B376317-7F7B-4301-8E61-934F619BAF0C.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: 0x0

Thread 0 (crashed)
 0  XUL!nsTHashtable<mozilla::places::History::KeyClass>::s_HashKey [nsURIHashKey.h : 41 + 0x0]
    rbx = 0x00000000   r12 = 0x70ac75e0   r13 = 0x0aeb5d10   r14 = 0x43d61f88
    r15 = 0x47db39d0   rip = 0x01da1268   rsp = 0x5fbfcd30   rbp = 0x072ef800
 1  XUL!PL_DHashTableOperate [pldhash.cpp : 576 + 0x5]
    rbx = 0x00000000   r12 = 0x0aeb5d10   r13 = 0x0aeb5d10   r14 = 0x43d61f88
    r15 = 0x47db39d0   rip = 0x01fcefb2   rsp = 0x5fbfcdc0   rbp = 0x072ef800
 2  XUL!mozilla::places::History::UnregisterVisitedCallback [nsTHashtable.h : 148 + 0xd]
    rbx = 0x47db3a50   r12 = 0x00000000   r13 = 0x0aeb5d10   r14 = 0x43d61f88
    r15 = 0x47db39d0   rip = 0x01d99f2e   rsp = 0x5fbfce30   rbp = 0x072ef800
 3  XUL!mozilla::dom::Link::~Link [Link.cpp : 472 + 0xc]
    rbx = 0x47db3a50   r12 = 0x00000000   r13 = 0x46c521c0   r14 = 0x43d61f88
    r15 = 0x47db39d0   rip = 0x014fd0e1   rsp = 0x5fbfce60   rbp = 0x072ef800
 4  XUL!nsHTMLAnchorElement::~nsHTMLAnchorElement [nsHTMLAnchorElement.cpp : 135 + 0xb]
    rbx = 0x47db39d0   r12 = 0x00000000   r13 = 0x46c521c0   r14 = 0x43d61f88
    r15 = 0x47db39d0   rip = 0x015b93f9   rsp = 0x5fbfce70   rbp = 0x072ef800
 5  XUL!nsNodeUtils::LastRelease [nsNodeUtils.cpp : 251 + 0xb]
    rbx = 0x47db39d0   r12 = 0x00000000   r13 = 0x46c521c0   r14 = 0x43d61f88
    r15 = 0x47db39d0   rip = 0x014be2a2   rsp = 0x5fbfce80   rbp = 0x072ef800
 6  XUL!nsGenericElement::Release [nsGenericElement.cpp : 5055 + 0x7]
    rbx = 0x12736dd8   r12 = 0x00000000   r13 = 0x46c521c0   r14 = 0x43d61f88
    r15 = 0x47db39d0   rip = 0x014adef7   rsp = 0x5fbfcec0   rbp = 0x47db39d0
 7  XUL!ContentUnbinder::UnbindSubtree [nsCOMPtr.h : 446 + 0x9]
    rbx = 0x43d61f20   r12 = 0x00000001   r13 = 0x46c521c0   r14 = 0x43d61f88
    r15 = 0x47db39d0   rip = 0x014b2ee6   rsp = 0x5fbfcee0   rbp = 0x0000004b
 8  XUL!ContentUnbinder::UnbindSubtree [nsGenericElement.cpp : 4428 + 0xc]
    rbx = 0x43d61f20   r12 = 0x00000001   r13 = 0x44de1300   r14 = 0x43d61f88
    r15 = 0x44de1100   rip = 0x014b310d   rsp = 0x5fbfcfe0   rbp = 0x0000004b
 9  XUL!ContentUnbinder::UnbindSubtree [nsGenericElement.cpp : 4428 + 0xc]
    rbx = 0x44c57900   r12 = 0x00000007   r13 = 0x43b68880   r14 = 0x44c57968
    r15 = 0x083e7e00   rip = 0x014b310d   rsp = 0x5fbfd0e0   rbp = 0x00000001
10  XUL!ContentUnbinder::Run [nsGenericElement.cpp : 4428 + 0xa]
    rbx = 0x00000003   r12 = 0x0745c000   r13 = 0x0864b448   r14 = 0x00000278
    r15 = 0x0000004f   rip = 0x014b33db   rsp = 0x5fbfd1e0   rbp = 0x0864b3e0
11  XUL!nsThread::ProcessNextEvent [nsThread.cpp : 624 + 0x5]
    rbx = 0x003267a0   r12 = 0x00000000   r13 = 0x003267c8   r14 = 0x5fbfd280
    r15 = 0x5fbfd2ef   rip = 0x0200e673   rsp = 0x5fbfd250   rbp = 0x8000ffff
12  XUL!NS_ProcessPendingEvents_P [nsThreadUtils.cpp : 163 + 0xd]
    rbx = 0x003267a0   r12 = 0x9f297afc   r13 = 0x00000014   r14 = 0x5fbfd2ef
    r15 = 0x00000000   rip = 0x01fcdcee   rsp = 0x5fbfd2e0   rbp = 0x00000000
}

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.