Closed
Bug 1270904
Opened 10 years ago
Closed 10 years ago
Crash in IPCError-browser | (msgtype=0x2C004E,name=PBrowser::Msg_GetTabCount) Processing error: message was deserialized, but the handler returned false (indicating failure)
Categories
(Core :: DOM: Content Processes, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1266484
People
(Reporter: jimm, Unassigned)
Details
(Keywords: crash)
Crash Data
#2 top crasher on aurora right now. This is a false return abort (the handler failed, we return false, and ipdl aborts the child) so we should be able to fix this pretty easily.
aurora:
https://crash-stats.mozilla.com/signature/?product=Firefox&dom_ipc_enabled=!__null__&signature=IPCError-browser+%7C+(msgtype%3D0x2C004E%2Cname%3DPBrowser%3A%3AMsg_GetTabCount)+Processing+error%3A+message+was+deserialized%2C+but+th&_columns=date&_columns=product&_columns=version&_columns=build_id&_columns=platform&_columns=reason&_columns=address&page=1#reports
nightly:
https://crash-stats.mozilla.com/signature/?product=Firefox&dom_ipc_enabled=!__null__&signature=IPCError-browser+%7C+(msgtype%3D0x2C004D%2Cname%3DPBrowser%3A%3AMsg_GetTabCount)+Processing+error%3A+message+was+deserialized%2C+but+th&_columns=date&_columns=product&_columns=version&_columns=build_id&_columns=platform&_columns=reason&_columns=address&page=1
|
Reporter | |
Updated•10 years ago
|
Summary: Crash in IPCError-browser | (msgtype=0x2C004E,name=PBrowser::Msg_GetTabCount) rocessing error: message was deserialized, but the handler returned false (indicating failure) → Crash in IPCError-browser | (msgtype=0x2C004E,name=PBrowser::Msg_GetTabCount) Processing error: message was deserialized, but the handler returned false (indicating failure)
|
|
Reporter | |
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•