781148 - Intermittent talos tp5n crash on www.bild.de/index.html [@ nsFrameManager::CaptureFrameState]

Status: RESOLVED INVALID

(Core :: Layout, defect)

Description

[Ed Morley [:emorley]]

Rev4 MacOSX Snow Leopard 10.6 mozilla-inbound talos tpn on 2012-08-08 03:47:50 PDT for push 9428d40e8ead

slave: talos-r4-snow-041

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

{
NOISE: MOZ_EVENT_TRACE sample 1344424135577 73
NOISE: MOZ_EVENT_TRACE sample 1344424135908 331
NOISE: MOZ_EVENT_TRACE sample 1344424135966 57
NOISE: MOZ_EVENT_TRACE sample 1344424136093 127
NOISE: MOZ_EVENT_TRACE sample 1344424136115 21
NOISE: MOZ_EVENT_TRACE sample 1344424136163 47
NOISE: MOZ_EVENT_TRACE sample 1344424136199 36
NOISE: MOZ_EVENT_TRACE sample 1344424136229 29
NOISE: MOZ_EVENT_TRACE sample 1344424136257 28
NOISE: MOZ_EVENT_TRACE sample 1344424136284 26
NOISE: Cycle 1(4): loaded http://localhost/page_load_test/tp5n/bild.de/www.bild.de/index.html (next: http://localhost/page_load_test/tp5n/guardian.co.uk/www.guardian.co.uk/index.html)
NOISE: MOZ_EVENT_TRACE sample 1344424136532 248
NOISE: MOZ_EVENT_TRACE sample 1344424136563 31
NOISE: RSS: Main: 247975936
NOISE: 
NOISE: 
NOISE: __FAILbrowser non-zero return code (256)__FAIL
NOISE: Found crashdump: /var/folders/Hs/HsDn6a9SG8idoIya6p9mtE+++TI/-Tmp-/tmpdJ98s4/profile/minidumps/094D65CC-AA79-46DA-993D-9ADA4E24274B.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: 0x2f25338

Thread 0 (crashed)
 0  XUL!nsFrameManager::CaptureFrameState [nsPlaceholderFrame.h : 153 + 0x6]
    rbx = 0x492a0578   r12 = 0x0317abf0   r13 = 0x44f5b1e8   r14 = 0x43de1920
    r15 = 0x0d15e800   rip = 0x011ebbac   rsp = 0x5fbfbc30   rbp = 0x5fbfbcd0
}

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.