Closed Bug 1312106 Opened 9 years ago Closed 9 years ago

Crash in mozalloc_abort | NS_DebugBreak | mozilla::ipc::FatalError | mozilla::gfx::PGPUChild::FatalError | mozilla::a11y::PDocAccessibleChild::FatalError | mozilla::a11y::PDocAccessibleChild::SendCOMProxy

Categories

(Core :: Disability Access APIs, defect)

Product:
Core
Component:
Disability Access APIs
Platform:
x86
Windows 7
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1312064

People

(Reporter: jchen, Unassigned)

Details

(Keywords: crash)

Crash Data

This bug was filed from the Socorro interface and is report bp-4cc6c9bb-be0a-4453-8c5f-758712161021. ============================================================= High volume crash that started with the 10-20 Nightly. It's already the #3 top crash for that Nightly on Windows with 87 crashes. The stack starts with several a11y frames, so I'm wondering if it's a result of bug 1310788 turning on a11y on e10s. Any thoughts, Aaron?
Flags: needinfo?(aklotz)
There are several other suspicious crashes that all started with the 10-20 Nightly: mozilla::ipc::FatalError | mozilla::a11y::PDocAccessibleParent::OnMessageReceived (e.g. bp-db730b7f-556f-454b-9a39-ba1cf2161021) mozalloc_abort | NS_DebugBreak | mozilla::ipc::LogicError | mozilla::a11y::PDocAccessible::Transition (e.g. bp-8805c401-942b-4cfa-b568-918572161021) (and possibly related) mozilla::mscom::IsProxy (e.g. bp-50c7468b-1398-4f32-a7f7-d325e2161021)
Crash Signature: [@ mozalloc_abort | NS_DebugBreak | mozilla::ipc::FatalError | mozilla::gfx::PGPUChild::FatalError | mozilla::a11y::PDocAccessibleChild::FatalError | mozilla::a11y::PDocAccessibleChild::SendCOMProxy] → [@ mozalloc_abort | NS_DebugBreak | mozilla::ipc::FatalError | mozilla::gfx::PGPUChild::FatalError | mozilla::a11y::PDocAccessibleChild::FatalError | mozilla::a11y::PDocAccessibleChild::SendCOMProxy] [@ mozilla::ipc::FatalError | mozilla::a11y::PDocAcces…
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(aklotz)
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.