Open Bug 1473600 Opened 6 years ago Updated 2 years ago

Crash in mozilla::ipc::FatalError | mozilla::ipc::IProtocol::HandleFatalError | mozilla::ipc::IPDLParamTraits<T>::Read

Categories

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

61 Branch
Unspecified
Windows 10
defect

Tracking

()

Tracking Status
firefox61 --- affected
firefox62 --- affected
firefox63 --- affected

People

(Reporter: lizzard, Unassigned)

References

Details

(Keywords: crash, Whiteboard: qa-not-actionable)

Crash Data

This bug was filed from the Socorro interface and is report bp-4d047037-63f8-4ca4-b906-ce6bb0180705. ============================================================= The crash volume in beta 62 looks higher than it is on release 61, which makes me think this may end up as a top crash on 62 release. Often a startup crash. Top 10 frames of crashing thread: 0 mozglue.dll MOZ_CrashOOL mfbt/Assertions.cpp:33 1 xul.dll mozilla::ipc::FatalError ipc/glue/ProtocolUtils.cpp:300 2 xul.dll mozilla::ipc::IProtocol::HandleFatalError ipc/glue/ProtocolUtils.cpp:531 3 xul.dll mozilla::ipc::IPDLParamTraits<mozilla::dom::ClonedMessageData>::Read ipc/ipdl/DOMTypes.cpp:169 4 xul.dll mozilla::dom::PBrowserChild::OnMessageReceived ipc/ipdl/PBrowserChild.cpp:2704 5 xul.dll mozilla::dom::PContentChild::OnMessageReceived ipc/ipdl/PContentChild.cpp:5316 6 xul.dll mozilla::ipc::MessageChannel::DispatchAsyncMessage ipc/glue/MessageChannel.cpp:2134 7 xul.dll mozilla::ipc::MessageChannel::DispatchMessageW ipc/glue/MessageChannel.cpp:2064 8 xul.dll mozilla::ipc::MessageChannel::RunMessage ipc/glue/MessageChannel.cpp:1910 9 xul.dll mozilla::ipc::MessageChannel::MessageTask::Run ipc/glue/MessageChannel.cpp:1943 =============================================================
I should correct that, the volume isn't higher but the rate is high (it's the #11 top crash in beta)
Looking at 62b3, b4 and b5, 54% of the crashes have the reason "MOZ_CRASH(IPC FatalError in the parent process!)", 44% have IPDL error: "Error deserializing 'data' (SerializedStructuredCloneBuffer) member of 'ClonedMessageData'". abort()ing as a result and 1.62% have "IPDL error: "unknown union type". abort()ing as a result."
Priority: -- → P3
See Also: → 1562616

Error deserializing 'data' (SerializedStructuredCloneBuffer) member of 'ClonedMessageData' (the error the crash linked in comment #2) is a different error from the one in bug 1562616 comment #0.

As comment #2 reflects, this crash “signature” is not specific enough to be useful.

Whiteboard: qa-not-actionable

Aggregating over MOZ_CRASH_REASON leads to:

Reason # Percentage
MOZ_CRASH(IPC FatalError in the parent process!) 786 83.53 %
IPDL error: "Error deserializing 'data' (SerializedStructuredCloneBuffer) member of 'ClonedMessageData'". abort()ing as a result. 87 9.25 %
3 IPDL error: "Error deserializing 'data' (SerializedStructuredCloneBuffer) member of 'SerializedStructuredCloneReadInfo'". abort()ing as a result. 30 3.19 %

and for versions:

Version # Percentage
78.6.0esr 681 72.37 %
92.0 87 9.25 %
78.14.0esr 55 5.84 %
92.0.1 22 2.34 %
78.14.0 11 1.17 %
78.13.0esr 10 1.06 %
92.1.1 10 1.06 %

So the "Sunday ditch" is probably explained by ESR and with newer versions there seem to be less problems. For the rest, comment 3 still applies.

Severity: critical → S2

Since the crash volume is low (less than 15 per week), the severity is downgraded to S3. Feel free to change it back if you think the bug is still critical.

For more information, please visit auto_nag documentation.

Severity: S2 → S3
You need to log in before you can comment on or make changes to this bug.