1342103 - Crash in IPCError-browser | <unknown IPC msg name> Unknown message: not processed

Status: RESOLVED WORKSFORME

(Core :: DOM: Content Processes, defect, P3)

Description

[(inactive) Jim Chen [:jchen] [:darchons]]

This bug was filed from the Socorro interface and is 
report bp-3a1ad9b1-c1d7-41f3-8825-d80ad2170223.
=============================================================

Low volume crash that appeared in the 02-21 Nightly on Windows. The message and stack appear very generic though; not sure if there's more useful information in the crash reports.

Comment 1

[Andrew McCreight [:mccr8]]

Some of the crashes have mozilla::dom::PContentChild::Read(mozilla::dom::XPCOMInitData*, IPC::Message const*, PickleIterator*) in the call stack, which suggests a regression from bug 1303096.

Some of them look kind of junky, but with a11y-ish stuff in there:
 bp-e28b8063-cb30-4ce9-b14b-2175f2170222

Maybe it is better to first figure out why the message says unknown, assuming it isn't just corruption.

Comment 2

[Andrew McCreight [:mccr8]]

I guess this could be a situation where the parent and child are running different builds? I think Bill said that was possible.

Comment 3

[Chris AtLee [:catlee]]

I get this crash often on one of my Firefox profiles when I try loading local HTML reference docs.

https://crash-stats.mozilla.com/report/index/8a0ecb60-40c8-4e96-9969-266272170224

Comment 4

[BugBot [:suhaib / :marco/ :calixte]]

Closing because no crashes reported for 12 weeks.

Comment 5

[BugBot [:suhaib / :marco/ :calixte]]

Bugbug thinks this bug is a regression, but please revert this change in case of error.