1125220 - mozilla::ipc::FatalError crash in mozilla::jsipc::PJavaScriptChild::Read

Status: RESOLVED WORKSFORME

(Core :: IPC, defect, P3)

Description

[alex_mayorga]

This bug was filed from the Socorro interface and is 
report bp-8ead4ae8-bdc2-470c-b9fd-1d6982150123.
=============================================================

Comment 1

[David Baron :dbaron: (⌚️UTC-5, no longer working on Mozilla)]

There seem to be a decent number of these crashes... although they seem to have gotten substantially more common in nightly around 2015-12-14:

https://crash-stats.mozilla.com/signature/?product=Firefox&release_channel=nightly&date=%3E%3D2015-08-01&signature=mozalloc_abort+|+NS_DebugBreak+|+mozilla%3A%3Aipc%3A%3AFatalError+|+mozilla%3A%3Ajsipc%3A%3APJavaScriptChild%3A%3ARead#aggregations

It's not clear to me whether it's worth separating the spike on December 14 into a separate bug -- or even how we distinguish different sorts of problems in these crash reports.

Comment 2

[Jed Davis [:jld] ⟨⏰|UTC-7⟩ ⟦he/him⟧]

Bug 1210821 comment #4 may be relevant.  I'm not sure if it makes much difference whether the PJavaScript{Child,Parent}::Read -> FatalError call is about an unexpected end of message or a bad enum discriminant (which are the two calls I see there) — either way, there's a sync IPC call that got a response not of the expected type, meaning that the IPC message layer got message ordering wrong and violated the IPDL layer's type safety.

Trying to find the cause beyond that from crash data may not be possible; I don't know that the code representing the root cause would still be on a stack at that point.

Comment 3

[Brad Lassey [:blassey] (use needinfo?)]

Bill, is this strictly add-on CPOW related?

Comment 4

[Bill McCloskey [inactive unless it's an emergency] (:billm)]

Yes, this is one of the IPC bugs I'm hoping to fix soon.

Comment 6

[alex_mayorga]

¡Hola!

None of the signatures on this bug has crashes in the past week, resolving.

¡Gracias!
Alex