Crash in [@ mozilla::ipc::FatalError | mozilla::dom::PContentParent::OnMessageReceived] with: Error deserializing 'PBrowser'
Categories
(Core :: DOM: Content Processes, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr78 | --- | unaffected |
firefox80 | --- | wontfix |
firefox81 | --- | wontfix |
firefox82 | --- | wontfix |
firefox83 | --- | fix-optional |
People
(Reporter: robwu, Unassigned)
Details
(Keywords: crash, regression)
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/e350a8c2-10c8-496f-8d6c-404e30200908
Top 3 frames of crashing thread:
0 XUL mozilla::ipc::FatalError ipc/glue/ProtocolUtils.cpp:188
1 XUL mozilla::dom::PContentParent::OnMessageReceived ipc/ipdl/PContentParent.cpp:12522
2 Foundation GCC_except_table6
Starting from Firefox 80.0, this crash is triggered with IPCFatalErrorMsg
set to Error deserializing 'PBrowser'
(you can see this field under the metadata tab of a crash report): link to all crash reports with the IPCFatalErrorMsg
column shown (note that it started with Firefox 80.*, and there is also a 81.0 beta among the reports).
When I search for Error deserializing 'PBrowser
and limit the results to PContentParent, then there are three results:
PContent::Msg_PWebBrowserPersistDocumentConstructor__ID
(unlikely - see below)PContent::Msg_CreateWindow__ID
PContent::Msg_CreateWindowInDifferentProcess__ID
According to the reported (who I am in contact with), the crash happened when they clicked on a button in a moz-extension:
document (tab), which in turn tried to open a new tab. So I think that the crash is triggered via CreateWindow
or CreateWindowInDifferentProcess
.
Reporter | ||
Comment 1•5 years ago
|
||
Nika, I saw that you've recently made some changes in the aThisTab
parameter of CreateWindow
in bug 1639367, which might be related to this crash.
Could you take a look at this crash report to see if anything stands out?
![]() |
||
Updated•5 years ago
|
Updated•5 years ago
|
Comment 2•5 years ago
|
||
S3 because the crash volume is low for now.
Updated•5 years ago
|
Comment 3•3 years ago
|
||
Closing because no crashes reported for 12 weeks.
Updated•1 year ago
|
Description
•