Jim Mathies [:jimm] Reporter
	Description • 9 years ago

mozilla::dom::PScreenManagerChild::SendScreenForBrowser occasionally fails, Causing an abort of the child process.

http://mxr.mozilla.org/mozilla-central/source/widget/nsScreenManagerProxy.cpp#129
http://mxr.mozilla.org/mozilla-central/source/dom/ipc/ScreenManagerParent.cpp#119

Looks like the recv side doesn't abort anywhere, similar to bug 1127378.

	Jim Mathies [:jimm] Reporter
	Comment 1 • 9 years ago

two crashes this has shown up under thus far:

1) mozilla::layers::PLayerTransactionChild::SendUpdate(nsTArray<mozilla::layers::Edit> const &,unsigned __int64 const &,mozilla::layers::TargetConfig const &,nsTArray<mozilla::layers::PluginWindowData> const &,bool const &,bool const &,unsigned int const &,bool const &,mozilla::TimeStamp const &,nsTArray<mozilla::layers::EditReply> *)

2) mozilla::dom::PScreenManagerChild::SendScreenForBrowser(mozilla::dom::IdType<mozilla::dom::TabParent> const &,mozilla::dom::ScreenDetails *,bool *)

common ipc error for both:
 '(msgtype=0x3E0004,name=PDocAccessible::Msg_ShowEvent) Processing error: message was deserialized, but the handler returned false (indicating failure)'

These failures are not very common at this point, see the parent bug for details.