Crash in [@ mozilla::ipc::FatalError | mozilla::ipc::IProtocol::HandleFatalError | mozilla::dom::PContentChild::OnMessageReceived] | Error deserializing 'BrowsingContext'
Categories
(Core :: DOM: Content Processes, defect, P3)
Tracking
()
| Fission Milestone | M5 |
| Tracking | Status | |
|---|---|---|
| firefox-esr60 | --- | unaffected |
| firefox66 | --- | unaffected |
| firefox67 | --- | unaffected |
| firefox68 | --- | fix-optional |
People
(Reporter: marcia, Unassigned)
References
Details
(Keywords: crash, regression)
Crash Data
This bug is for crash report bp-ff31c60c-550d-4f90-9b5d-fea440190415.
Small cross platform spike on nightly 68 which started in 20190415213626: https://bit.ly/2De0zko
All crashes have Moz Crash reason: IPDL error: "Error deserializing 'RefPtr'". abort()ing as a result.
Possible regression range based on Build ID: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=adc32d869e58d0c052094f718bc9e4cff8390be4&tochange=b8f49a14c458f56a6a08e4c177671108e386be3a
The only IPC related bug in that range is Bug 1494469, unless the crash is being caused by something else.
Top 10 frames of crashing thread:
0 XUL mozilla::ipc::FatalError ipc/glue/ProtocolUtils.cpp:264
1 XUL mozilla::ipc::IProtocol::HandleFatalError const ipc/glue/ProtocolUtils.cpp:440
2 XUL mozilla::dom::PContentChild::OnMessageReceived ipc/ipdl/PContentChild.cpp
3 XUL mozilla::ipc::MessageChannel::DispatchMessage ipc/glue/MessageChannel.cpp:2151
4 XUL mozilla::ipc::MessageChannel::MessageTask::Run ipc/glue/MessageChannel.cpp:1968
5 XUL nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:1180
6 XUL NS_ProcessNextEvent xpcom/threads/nsThreadUtils.cpp:486
7 XUL mozilla::ipc::MessagePump::Run ipc/glue/MessagePump.cpp:110
8 XUL nsBaseAppShell::Run widget/nsBaseAppShell.cpp:137
9 XUL nsAppShell::Run widget/cocoa/nsAppShell.mm:704
| Reporter | ||
Comment 1•7 years ago
|
||
ni on Jed Davis to see if he can clarify what might have caused this small spike.
Comment 2•7 years ago
|
||
It could be related to changes about BrowsingContext too.
:nika, could you have look please ?
Comment 4•7 years ago
|
||
I'm inclined to wait for :jld's work on bug 1544825, as it can greatly improve diagnostics and help figure out what might be going on here.
Until bug 1544421, we didn't actually check validity of BrowsingContext within the deserializer correctly, so I doubt it's caused by that in particular.
Comment 5•7 years ago
|
||
(In reply to :Nika Layzell (ni? for response) from comment #4)
I'm inclined to wait for :jld's work on bug 1544825, as it can greatly improve diagnostics and help figure out what might be going on here.
The patch I have will tell us what type is causing the problem, but if it's something complex like nsIInputStream there's still a lot of information about what went wrong that won't be captured.
Updated•7 years ago
|
Updated•7 years ago
|
Updated•7 years ago
|
Updated•7 years ago
|
Comment 6•7 years ago
|
||
In the last week it looks like we've had:
- IPDL error: "Error deserializing 'BrowsingContext'". abort()ing as a result. e.g. bp-4ff7f756-4a2d-4a59-92af-d067f0190427
- incorrect sentinel when reading Error deserializing 'uint64_t' e.g. bp-4425d869-12ef-43cb-90b0-ee1e60190429
- incorrect sentinel when reading Error deserializing 'name' (nsCString) member of 'PluginTag' e.g. bp-4a289046-c79f-414b-bdeb-93fed0190425
Comment 7•7 years ago
|
||
The priority flag is not set for this bug.
:jld, could you have a look please?
For more information, please visit auto_nag documentation.
Comment 8•7 years ago
|
||
Breaking down the recent failures under this bug's crash signatures by Ipc fatal error msg, there are a lot of Error deserializing 'PBrowserParent' but they're only on ESR. Limiting to Nightly, it's only Error deserializing 'BrowsingContext' (the other ones mentioned in comment #6 have different signatures), so I'm handing this over to DOM.
| Reporter | ||
Comment 9•7 years ago
|
||
20 crashes/10 installs in the last 7 days.
Here are a few URLs:
Updated•7 years ago
|
Comment 12•7 years ago
|
||
The priority flag is not set for this bug.
:jimm, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•7 years ago
|
Updated•7 years ago
|
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
Comment 16•7 years ago
|
||
I have encountered this issue while fast scrolling through 9gag.com with fission enabled.
bp-0ed6613a-3836-4f22-ac78-d157a0190710
| Comment hidden (Intermittent Failures Robot) |
Updated•7 years ago
|
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
| Comment hidden (Intermittent Failures Robot) |
Comment 25•6 years ago
|
||
WFM. No crash reports since December. This crash signature is extremely generic and not useful.
Description
•