Closed Bug 759706 Opened 13 years ago Closed 12 years ago

Intermittent tprow crash on blogfa.com/blogfa.com/index.html [@ RuleHash_TagTable_ClearEntry]

Categories

(Core :: CSS Parsing and Computation, defect)

Product:
Core
Component:
CSS Parsing and Computation
Platform:
x86_64
macOS
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
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 tprow on 2012-05-29 21:19:19 PDT for push 4b57d0e84255 slave: talos-r4-snow-041 https://tbpl.mozilla.org/php/getParsedLog.php?id=12182337&tree=Firefox#error0 { NOISE: MOZ_EVENT_TRACE sample 1338352640968 58 NOISE: MOZ_EVENT_TRACE sample 1338352641078 110 NOISE: Cycle 1(12): loaded http://localhost/page_load_test/tp5/naver.com/www.naver.com/index.html (next: http://localhost/page_load_test/tp5/blogfa.com/blogfa.com/index.html) NOISE: MOZ_EVENT_TRACE sample 1338352641232 154 NOISE: RSS: Main: 231735296 NOISE: NOISE: MOZ_EVENT_TRACE sample 1338352641532 83 NOISE: MOZ_EVENT_TRACE sample 1338352641553 20 NOISE: MOZ_EVENT_TRACE sample 1338352641588 34 NOISE: MOZ_EVENT_TRACE sample 1338352641617 28 NOISE: NOISE: __FAILbrowser non-zero return code (256)__FAIL NOISE: Found crashdump: /var/folders/Hs/HsDn6a9SG8idoIya6p9mtE+++TI/-Tmp-/tmpuadClY/profile/minidumps/35FFBD3F-7417-4446-A474-926E1BD17DB9.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: 0x42db5400 Thread 0 (crashed) 0 XUL!RuleHash_TagTable_ClearEntry [mozilla-central:.h:4b57d0e84255 : 225 + 0x0] rbx = 0x47ffa570 r12 = 0x47ffa5b8 r13 = 0x2505ec68 r14 = 0x48000000 r15 = 0x5fbfc290 rip = 0x01330b82 rsp = 0x5fbfbf00 rbp = 0x47ffa578 1 XUL!PL_DHashTableFinish [pldhash.cpp : 360 + 0x9] rbx = 0x47ffa5b8 r12 = 0x47ffa5b8 r13 = 0x2505ec68 r14 = 0x48000000 r15 = 0x5fbfc290 rip = 0x01fd0cf2 rsp = 0x5fbfbf20 rbp = 0x00000048 2 XUL!RuleHash::~RuleHash [nsCSSRuleProcessor.cpp : 584 + 0x8] rbx = 0x2505ec00 r12 = 0x25055460 r13 = 0x00000006 r14 = 0x25055470 r15 = 0x5fbfc290 rip = 0x0132ecb5 rsp = 0x5fbfbf50 rbp = 0x00000000 3 XUL!nsCSSRuleProcessor::~nsCSSRuleProcessor [nsCSSRuleProcessor.cpp : 959 + 0x7] rbx = 0x2505ec00 r12 = 0x25055460 r13 = 0x00000006 r14 = 0x25055470 r15 = 0x5fbfc290 rip = 0x013309a2 rsp = 0x5fbfbf60 rbp = 0x00000000 4 XUL!nsCSSRuleProcessor::Release [nsCSSRuleProcessor.cpp : 1071 + 0x5] rbx = 0x00000000 r12 = 0x252f7780 r13 = 0x411e0d00 r14 = 0x02fea460 r15 = 0x5fbfc290 rip = 0x0132a70a rsp = 0x5fbfbf90 rbp = 0x252f77c0 5 XUL!PresShell::~PresShell [mozilla-central::4b57d0e84255 : 446 + 0x7] rbx = 0x252f77c0 r12 = 0x252f7780 r13 = 0x411e0d00 r14 = 0x02fea460 r15 = 0x5fbfc290 rip = 0x01244fec rsp = 0x5fbfbfa0 rbp = 0x252f77c0 6 XUL!PresShell::Release [nsPresShell.cpp : 672 + 0x8] rbx = 0x00000000 r12 = 0x5fbfc0f0 r13 = 0x5fbfc010 r14 = 0x02fea460 r15 = 0x5fbfc290 rip = 0x01232e06 rsp = 0x5fbfbfe0 rbp = 0x5fbfc000 7 XUL!DocumentViewerImpl::DestroyPresShell [mozilla-central::4b57d0e84255 : 617 + 0xa] rbx = 0x23a3bdc0 r12 = 0x5fbfc0f0 r13 = 0x5fbfc010 r14 = 0x02fea460 r15 = 0x5fbfc290 rip = 0x0121391a rsp = 0x5fbfbff0 rbp = 0x5fbfc000 8 XUL!DocumentViewerImpl::Destroy [nsDocumentViewer.cpp : 1651 + 0x7] rbx = 0x23a3bdc0 r12 = 0x5fbfc0f0 r13 = 0x5fbfc150 r14 = 0x02fea460 r15 = 0x5fbfc290 rip = 0x01214084 rsp = 0x5fbfc050 rbp = 0x45ebb600 9 XUL!nsDocShell::Destroy [nsDocShell.cpp : 4685 + 0x5] rbx = 0x00000000 r12 = 0x5fbfc0f0 r13 = 0x5fbfc150 r14 = 0x02fea460 r15 = 0x5fbfc290 rip = 0x01bbfaea rsp = 0x5fbfc0e0 rbp = 0x23a36c00 10 XUL!nsFrameLoader::Finalize [nsFrameLoader.cpp : 542 + 0x5] rbx = 0x23fc4390 r12 = 0x00000001 r13 = 0x5fbfc150 r14 = 0x02fea460 r15 = 0x5fbfc290 rip = 0x01491f7b rsp = 0x5fbfc120 rbp = 0x00000000 }
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][red] → [red]
You need to log in before you can comment on or make changes to this bug.