Closed Bug 782931 Opened 7 years ago Closed 7 years ago

Intermittent tp5n crash on people.com.cn [@ nsHtml5HtmlAttributes::getLocalName]

Categories

(Core :: HTML: Parser, defect, critical)

x86_64
macOS
defect
Not set
critical

Tracking

()

RESOLVED INVALID

People

(Reporter: emorley, Unassigned)

References

Details

(Keywords: crash, intermittent-failure, Whiteboard: [red])

Crash Data

Rev4 MacOSX Snow Leopard 10.6 mozilla-central talos tpn on 2012-08-15 04:08:54 PDT for push 86ee4deea55b

slave: talos-r4-snow-013

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

{
NOISE: MOZ_EVENT_TRACE sample 1345030527112 27
NOISE: MOZ_EVENT_TRACE sample 1345030527215 102
NOISE: MOZ_EVENT_TRACE sample 1345030527434 218
NOISE: Cycle 1(24): loaded http://localhost/page_load_test/tp5n/youtube.com/www.youtube.com/music.html (next: http://localhost/page_load_test/tp5n/people.com.cn/people.com.cn/index.html)
NOISE: MOZ_EVENT_TRACE sample 1345030527591 157
NOISE: RSS: Main: 189153280
NOISE: 
NOISE: MOZ_EVENT_TRACE sample 1345030527869 47
NOISE: MOZ_EVENT_TRACE sample 1345030527957 87
NOISE: 
NOISE: __FAILbrowser non-zero return code (256)__FAIL
NOISE: Found crashdump: /var/folders/Hs/HsDn6a9SG8idoIya6p9mtE+++TI/-Tmp-/tmpMVxXaj/profile/minidumps/3C0B03CE-00B2-4376-B551-3530E3D2E61D.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 / 0x0000000d
Crash address: 0x0

Thread 0 (crashed)
 0  XUL!nsHtml5HtmlAttributes::getLocalName [nsHtml5HtmlAttributes.cpp : 97 + 0x0]
    rbx = 0x43c30a00   r12 = 0x04a8d7c0   r13 = 0x459f1e00   r14 = 0x0b055ac8
    r15 = 0x676e6962   rip = 0x017c50b4   rsp = 0x5fbfc430   rbp = 0x5fbfc430
}
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: 7 years ago
Resolution: --- → INVALID
Whiteboard: [orange][red] → [red]
You need to log in before you can comment on or make changes to this bug.