Closed Bug 1329816 Opened 8 years ago Closed 8 years ago

Crash in mozilla::ipc::FatalError | mozilla::ipc::IProtocol::HandleFatalError | mozilla::ipc::IProtocol::FatalError | mozilla::dom::PBrowserParent::OnMessageReceived

Categories

(Core :: Disability Access APIs, defect)

50 Branch
All
Windows
defect
Not set
critical

Tracking

()

RESOLVED FIXED
Tracking Status
firefox52 + disabled
firefox53 + disabled
firefox54 + disabled

People

(Reporter: RyanVM, Assigned: bugzilla)

References

Details

(Keywords: crash, Whiteboard: aes+)

Crash Data

This bug was filed from the Socorro interface and is report bp-90cc23a1-ba8d-4ed0-939e-0dcdb2170109. ============================================================= Currently the #9 topcrasher on Aurora. Appears to be Windows-only, but that might be population size too.
Flags: needinfo?(wmccloskey)
[Tracking Requested - why for this release]: Top crash
In all the crashes I looked at, the IPCFatalErrorMsg string reports: "Error deserializing 'IAccessibleHolder'". Aaron, can you take a look at this?
Component: IPC → Disability Access APIs
Flags: needinfo?(wmccloskey) → needinfo?(aklotz)
Very much related to bug 1325834, though that one tends to be in the child process instead of the parent. Not sure whether or not it's precisely a dup, though.
Flags: needinfo?(aklotz)
Whiteboard: aes+
Since I'm already assigned to bug 1325834...
Assignee: nobody → aklotz
Depends on: 1325834
[Tracking Requested - why for this release]: We want to ship a11y+e10s in 54.
Tracking 54+ for the reason in Comment 5.
Crash Signature: [@ mozilla::ipc::FatalError | mozilla::ipc::IProtocol::HandleFatalError | mozilla::ipc::IProtocol::FatalError | mozilla::dom::PBrowserParent::OnMessageReceived] → [@ mozilla::ipc::FatalError | mozilla::ipc::IProtocol::HandleFatalError | mozilla::ipc::IProtocol::FatalError | mozilla::dom::PBrowserParent::OnMessageReceived] [@ mozilla::ipc::FatalError | mozilla::a11y::PDocAccessibleParent::OnMessageReceived]
This hasn't been seen on 55 for a few weeks now. Resolving.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.