780889 - Intermittent talos tp5n crash on www.bild.de/index.html [@ js::gc::MarkString]

Status: RESOLVED INVALID

(Core :: JavaScript Engine, defect)

Description

[Ed Morley [:emorley]]

See also bug 780611, which occurs on the same page.

Rev4 MacOSX Snow Leopard 10.6 mozilla-inbound talos tpn on 2012-08-06 23:31:19 PDT for push 707a4a6340f0

slave: talos-r4-snow-041

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

{
NOISE: MOZ_EVENT_TRACE sample 1344322300743 28
NOISE: MOZ_EVENT_TRACE sample 1344322300828 74
NOISE: MOZ_EVENT_TRACE sample 1344322301160 332
NOISE: MOZ_EVENT_TRACE sample 1344322301218 58
NOISE: MOZ_EVENT_TRACE sample 1344322301347 129
NOISE: MOZ_EVENT_TRACE sample 1344322301368 20
NOISE: MOZ_EVENT_TRACE sample 1344322301389 21
NOISE: MOZ_EVENT_TRACE sample 1344322301417 28
NOISE: MOZ_EVENT_TRACE sample 1344322301454 36
NOISE: MOZ_EVENT_TRACE sample 1344322301479 24
NOISE: MOZ_EVENT_TRACE sample 1344322301513 33
NOISE: MOZ_EVENT_TRACE sample 1344322301540 27
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: 
NOISE: __FAILbrowser non-zero return code (256)__FAIL
NOISE: Found crashdump: /var/folders/Hs/HsDn6a9SG8idoIya6p9mtE+++TI/-Tmp-/tmptU2SdC/profile/minidumps/6265B7B8-229F-4A69-8B78-91543F92A72A.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!js::gc::MarkString [Heap.h : 1010 + 0x0]
    rbx = 0x4c22d540   r12 = 0x00000000   r13 = 0x4c22d540   r14 = 0x0628b1d0
    r15 = 0x0628b1c0   rip = 0x02590de9   rsp = 0x5fbfb910   rbp = 0x5fbfb920
}

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.