Closed Bug 1312064 Opened 8 years ago Closed 8 years ago

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

Categories

(Core :: Disability Access APIs, defect)

48 Branch
Unspecified
Windows 10
defect
Not set
critical

Tracking

()

RESOLVED FIXED
Tracking Status
firefox52 + fixed
firefox53 + fixed

People

(Reporter: jimm, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash, Whiteboard: aes+ (work happening on bug 1314707))

Crash Data

In the 3-day list this is currently #26. This bug was filed from the Socorro interface and is report bp-082e5b65-39f7-4a3b-8add-db1e62161021.
Crash Signature: [@ mozalloc_abort | NS_DebugBreak | mozilla::ipc::FatalError | mozilla::a11y::PDocAccessibleChild::SendCOMProxy] → [@ mozalloc_abort | NS_DebugBreak | mozilla::ipc::FatalError | mozilla::a11y::PDocAccessibleChild::SendCOMProxy] [@ mozalloc_abort | NS_DebugBreak | mozilla::ipc::FatalError | mozilla::layers::PCompositorBridgeChild::FatalError | mozilla::a11y::PDocAcces…
Crash Signature: mozilla::a11y::PDocAccessibleChild::FatalError | mozilla::a11y::PDocAccessibleChild::SendCOMProxy] → mozilla::a11y::PDocAccessibleChild::FatalError | mozilla::a11y::PDocAccessibleChild::SendCOMProxy] [@ mozalloc_abort | NS_DebugBreak | mozilla::ipc::LogicError | mozilla::a11y::PDocAccessible::Transition]
Crash Signature: mozilla::a11y::PDocAccessibleChild::FatalError | mozilla::a11y::PDocAccessibleChild::SendCOMProxy] [@ mozalloc_abort | NS_DebugBreak | mozilla::ipc::LogicError | mozilla::a11y::PDocAccessible::Transition] → mozilla::a11y::PDocAccessibleChild::FatalError | mozilla::a11y::PDocAccessibleChild::SendCOMProxy] [@ mozalloc_abort | NS_DebugBreak | mozilla::ipc::LogicError | mozilla::a11y::PDocAccessible::Transition] [@ IPCError-browser | PBrowser::Msg_PDocAccessi…
Crash Signature: PBrowser::Msg_PDocAccessibleConstructor Processing error: message was deserialized, but the handler ] → PBrowser::Msg_PDocAccessibleConstructor Processing error: message was deserialized, but the handler ] [@ mozalloc_abort | NS_DebugBreak | mozilla::ipc::FatalError | mozilla::dom::PContentBridgeChild::FatalError | mozilla::a11y::PDocAccessibleChild::Fata…
Is this a duplication of bug 1270916 and bug 1307414?
Crash Signature: , but the handler ] [@ mozalloc_abort | NS_DebugBreak | mozilla::ipc::FatalError | mozilla::dom::PContentBridgeChild::FatalError | mozilla::a11y::PDocAccessibleChild::FatalError | mozilla::a11y::PDocAccessibleChild::SendCOMProxy] → , but the handler ] [@ mozalloc_abort | NS_DebugBreak | mozilla::ipc::FatalError | mozilla::dom::PContentBridgeChild::FatalError | mozilla::a11y::PDocAccessibleChild::FatalError | mozilla::a11y::PDocAccessibleChild::SendCOMProxy]
Crash Signature: mozilla::a11y::PDocAccessibleChild::FatalError | mozilla::a11y::PDocAccessibleChild::SendCOMProxy] [@ mozalloc_abort | NS_DebugBreak | mozilla::ipc::LogicError | mozilla::a11y::PDocAccessible::Transition] [@ IPCError-browser | PBrowser::Msg_PDocAccessi… → mozilla::a11y::PDocAccessibleChild::FatalError | mozilla::a11y::PDocAccessibleChild::SendCOMProxy] [@ mozalloc_abort | NS_DebugBreak | mozilla::ipc::LogicError | mozilla::a11y::PDocAccessible::Transition] [@ mozalloc_abort | NS_DebugBreak | mozilla::ip…
#3 top crash of Nightly 20161030030204 on Windows.
Crash Signature: mozilla::ipc::FatalError | mozilla::dom::PContentBridgeChild::FatalError | mozilla::a11y::PDocAccessibleChild::FatalError | mozilla::a11y::PDocAccessibleChild::SendCOMProxy] → mozilla::ipc::FatalError | mozilla::dom::PContentBridgeChild::FatalError | mozilla::a11y::PDocAccessibleChild::FatalError | mozilla::a11y::PDocAccessibleChild::SendCOMProxy] [ @mozalloc_abort | NS_DebugBreak | mozilla::ipc::FatalError | mozilla::layers:…
Crash Signature: mozilla::ipc::FatalError | mozilla::dom::PContentBridgeChild::FatalError | mozilla::a11y::PDocAccessibleChild::FatalError | mozilla::a11y::PDocAccessibleChild::SendCOMProxy] [ @mozalloc_abort | NS_DebugBreak | mozilla::ipc::FatalError | → mozilla::ipc::FatalError | mozilla::dom::PContentBridgeChild::FatalError | mozilla::a11y::PDocAccessibleChild::FatalError | mozilla::a11y::PDocAccessibleChild::SendCOMProxy] [@ mozalloc_abort | NS_DebugBreak | mozilla::ipc::FatalError |
Crash Signature: mozilla::layers::PImageBridgeChild::FatalError | mozilla::a11y::PDocAccessibleChild::FatalError | mozilla::a11y::PDocAccessibleChild::SendCOMProxy] → mozilla::layers::PImageBridgeChild::FatalError | mozilla::a11y::PDocAccessibleChild::FatalError | mozilla::a11y::PDocAccessibleChild::SendCOMProxy] [@ mozalloc_abort | NS_DebugBreak | mozilla::ipc::FatalError | mozilla::ipc::IProtocol::HandleFatalError …
In Aurora 20161127004009 crashes with these signatures are in positions #2, #4, #11 on the top crash list. In Nightly 20161127030208 one of them is at #14. dbolter, how should we proceed here? This bug is unloved and getting old.
Flags: needinfo?(dbolter)
(In reply to Nicholas Nethercote [:njn] from comment #5) > In Aurora 20161127004009 crashes with these signatures are in positions #2, > #4, #11 on the top crash list. > > In Nightly 20161127030208 one of them is at #14. > > dbolter, how should we proceed here? This bug is unloved and getting old. bug 1314707 will hopefully fix it. If not it will at least change the signature. Me and aklotz were both off last week so I'm just getting to review that.
Clearing NI - see comment 6.
Whiteboard: aes+ → aes+ (work happening on bug 1314707)
Tracking 53+/52+ for this crash - a fair number of signatures in top positions on Aurora and still one on nightly.
Flags: needinfo?(dbolter)
Still a topcrash on Nightly and Aurora. Any word on progress?
Flags: needinfo?(tbsaunde+mozbugs)
(In reply to Nicholas Nethercote [:njn] from comment #9) > Still a topcrash on Nightly and Aurora. Any word on progress? Entirely dependent on bug 1321935, which is r?tbsaunde, so I'll leave this ni? in place.
Depends on: 1321935
I think I've handled all the deps so canceling ni?
Flags: needinfo?(tbsaunde+mozbugs)
Bug 1314707 took care of this, resolving.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
We're going to have to sever that signature from this bug and treat it separately. SendCOMProxy doesn't even exist anymore as an IPC message, so wherever this is now happening, it is a distinct location in the code from this bug.
Flags: needinfo?(aklotz)
You need to log in before you can comment on or make changes to this bug.