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

This is our one remaining a11y KillHard abort, which is on par with bug 1189277 in terms of frequency. I swear this is filed someplace else, but maybe I'm just confusing it with bugs like bug 1170153, and bug 1181177.

In any case we need to get this fixed, like bug 1189277 it causes random failures in random ipc apis.

IPC error breakdown per KillHard signature:
----------------------------------------------------
mozilla::dom::PBrowserChild::SendGetTabOffset(mozilla::gfx::IntPointTyped<mozilla::LayoutDevicePixel> *):
  1 - '(msgtype=0x3C0002,name=???) Route error: message sent to unknown actor ID'
  1 - 'HangMonitor'
  45 - '(msgtype=0x200006,name=PBrowser::Msg_PDocAccessibleConstructor) Processing error: message was deserialized, but the handler returned false (indicating failure)'
  18 - '(msgtype=0x4A0008,name=PDocAccessible::Msg_BindChildDoc) Processing error: message was deserialized, but the handler returned false (indicating failure)'

SendRpcMessage(..):
  1 - '(msgtype=0x3C0002,name=???) Route error: message sent to unknown actor ID'
  9 - '(msgtype=0x200014,name=???) Message not allowed: cannot be sent/recvd in this state'
  14 - 'HangMonitor'
  30 - '(msgtype=0x200006,name=PBrowser::Msg_PDocAccessibleConstructor) Processing error: message was deserialized, but the handler returned false (indicating failure)'
  9 - '(msgtype=0x4A0008,name=PDocAccessible::Msg_BindChildDoc) Processing error: message was deserialized, but the handler returned false (indicating failure)'

mozilla::net::PCookieServiceChild::SendGetCookieString(..):
  1 - 'HangMonitor'
  14 - '(msgtype=0x200006,name=PBrowser::Msg_PDocAccessibleConstructor) Processing error: message was deserialized, but the handler returned false (indicating failure)'
  11 - '(msgtype=0x4A0008,name=PDocAccessible::Msg_BindChildDoc) Processing error: message was deserialized, but the handler returned false (indicating failure)'

mozilla::plugins::PPluginWidgetChild::SendGetNativePluginPort(..):
  1 - '(msgtype=0xA40006,name=???) Message not allowed: cannot be sent/recvd in this state'
  13 - '(msgtype=0x200006,name=PBrowser::Msg_PDocAccessibleConstructor) Processing error: message was deserialized, but the handler returned false (indicating failure)'
  2 - '(msgtype=0x4A0008,name=PDocAccessible::Msg_BindChildDoc) Processing error: message was deserialized, but the handler returned false (indicating failure)'

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> *):
  12 - '(msgtype=0x200006,name=PBrowser::Msg_PDocAccessibleConstructor) Processing error: message was deserialized, but the handler returned false (indicating failure)'
  3 - '(msgtype=0x4A0008,name=PDocAccessible::Msg_BindChildDoc) Processing error: message was deserialized, but the handler returned false (indicating failure)'

mozilla::dom::PScreenManagerChild::SendScreenForBrowser(mozilla::dom::IdType<mozilla::dom::TabParent> const &,mozilla::dom::ScreenDetails *,bool *):
  6 - '(msgtype=0x200006,name=PBrowser::Msg_PDocAccessibleConstructor) Processing error: message was deserialized, but the handler returned false (indicating failure)'
  4 - '(msgtype=0x4A0008,name=PDocAccessible::Msg_BindChildDoc) Processing error: message was deserialized, but the handler returned false (indicating failure)'

mozilla::dom::PContentChild::SendClipboardHasType(nsTArray<nsCString> const &,int const &,bool *):
  8 - '(msgtype=0x3A00A5,name=???) Message not allowed: cannot be sent/recvd in this state'

mozilla::dom::PBrowserChild::SendGetInputContext(..):
  1 - '(msgtype=0x3C0002,name=???) Route error: message sent to unknown actor ID'
  2 - 'HangMonitor'
  1 - '(msgtype=0x200006,name=PBrowser::Msg_PDocAccessibleConstructor) Processing error: message was deserialized, but the handler returned false (indicating failure)'
  4 - '(msgtype=0x4A0008,name=PDocAccessible::Msg_BindChildDoc) Processing error: message was deserialized, but the handler returned false (indicating failure)'

mozilla::plugins::PPluginWidgetChild::SendCreate(nsresult *):
  5 - '(msgtype=0xA40003,name=PPluginWidget::Msg_Create) Processing error: message was deserialized, but the handler returned false (indicating failure)'

mozilla::dom::PContentChild::SendClipboardHasType(nsTArray<nsCString> const&, int const&, bool*):
  4 - '(msgtype=0x3A00A5,name=???) Message not allowed: cannot be sent/recvd in this state'

SendSyncMessage(..):
  2 - 'HangMonitor'
  1 - '(msgtype=0x200006,name=PBrowser::Msg_PDocAccessibleConstructor) Processing error: message was deserialized, but the handler returned false (indicating failure)'

mozilla::dom::PBrowserChild::SendNotifyIMEFocus(mozilla::ContentCache const &,mozilla::widget::IMENotification const &,nsIMEUpdatePreference *):
  3 - '(msgtype=0x4A0008,name=PDocAccessible::Msg_BindChildDoc) Processing error: message was deserialized, but the handler returned false (indicating failure)'

mozilla::jsipc::PJavaScriptChild::SendCallOrConstruct(unsigned __int64 const &,nsTArray<mozilla::jsipc::JSParam> const &,bool const &,mozilla::jsipc::ReturnStatus *,mozilla::jsipc::JSVariant *,nsTArray<mozilla::jsipc::JSParam> *):
  3 - '(msgtype=0x200006,name=PBrowser::Msg_PDocAccessibleConstructor) Processing error: message was deserialized, but the handler returned false (indicating failure)'

mozilla::dom::PBlobChild::SendWaitForSliceCreation():
  2 - '(msgtype=0x160003,name=PBlob::Msg_PBlobStreamConstructor) Processing error: message was deserialized, but the handler returned false (indicating failure)'

mozilla::dom::PContentChild::SendGetRandomValues(unsigned int const &,nsTArray<unsigned char> *):
  2 - '(msgtype=0x200006,name=PBrowser::Msg_PDocAccessibleConstructor) Processing error: message was deserialized, but the handler returned false (indicating failure)'

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

s / one remaining / one of two remaining

if you include bug 1189277.

	Trevor Saunders (:tbsaunde)
	Comment 2 • 9 years ago

It  seems reasonably possible this is the same issue as bug 1189277, so I think it probably makes sense to see what happens here when builds with that fixed go out.

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

(In reply to Trevor Saunders (:tbsaunde) from comment #2)
> It  seems reasonably possible this is the same issue as bug 1189277, so I
> think it probably makes sense to see what happens here when builds with that
> fixed go out.

These are still showing up, but in much lower numbers.


Bug 1116884 KillHard child signature breakdown:
----------------------------------------------------
10	47.6%	SendRpcMessage(..)
3	14.3%	mozilla::net::PCookieServiceChild::SendGetCookieString(..)
2	9.5%	mozilla::plugins::PPluginWidgetChild::SendGetNativePluginPort(..)
2	9.5%	mozilla::dom::PContentChild::SendClipboardHasType(nsTArray<nsCString> const&, int const&, bool*)
2	9.5%	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 &,int const &,nsTArray<mozilla::layers::EditReply> *)
1	4.8%	mozilla::dom::PScreenManagerChild::SendScreenForBrowser(mozilla::dom::IdType<mozilla::dom::TabParent> const &,mozilla::dom::ScreenDetails *,bool *)
1	4.8%	mozilla::dom::PBrowserChild::SendGetTabOffset(mozilla::gfx::IntPointTyped<mozilla::LayoutDevicePixel> *)

IPC error breakdown per KillHard signature:
----------------------------------------------------
SendRpcMessage(..):
  2 - '(msgtype=0x3C0002,name=???) Route error: message sent to unknown actor ID'
  4 - '(msgtype=0x200015,name=???) Message not allowed: cannot be sent/recvd in this state'
  1 - '(msgtype=0x3A0092,name=???) Message not allowed: cannot be sent/recvd in this state'
  4 - 'HangMonitor'

mozilla::net::PCookieServiceChild::SendGetCookieString(..):
  2 - 'HangMonitor'
  2 - '(msgtype=0x200006,name=PBrowser::Msg_PDocAccessibleConstructor) Processing error: message was deserialized, but the handler returned false (indicating failure)'

mozilla::plugins::PPluginWidgetChild::SendGetNativePluginPort(..):
  2 - '(msgtype=0x200006,name=PBrowser::Msg_PDocAccessibleConstructor) Processing error: message was deserialized, but the handler returned false (indicating failure)'
  1 - '(msgtype=0x4A0008,name=PDocAccessible::Msg_BindChildDoc) Processing error: message was deserialized, but the handler returned false (indicating failure)'

mozilla::dom::PContentChild::SendClipboardHasType(nsTArray<nsCString> const&, int const&, bool*):
  3 - '(msgtype=0x3A00A5,name=???) Message not allowed: cannot be sent/recvd in this state'

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 &,int const &,nsTArray<mozilla::layers::EditReply> *):
  3 - '(msgtype=0x200006,name=PBrowser::Msg_PDocAccessibleConstructor) Processing error: message was deserialized, but the handler returned false (indicating failure)'

mozilla::dom::PScreenManagerChild::SendScreenForBrowser(mozilla::dom::IdType<mozilla::dom::TabParent> const &,mozilla::dom::ScreenDetails *,bool *):
  2 - '(msgtype=0xBE0009,name=???) Message not allowed: cannot be sent/recvd in this state'

mozilla::dom::PBrowserChild::SendGetTabOffset(mozilla::gfx::IntPointTyped<mozilla::LayoutDevicePixel> *):
  2 - '(msgtype=0x200006,name=PBrowser::Msg_PDocAccessibleConstructor) Processing error: message was deserialized, but the handler returned false (indicating failure)'

	Trevor Saunders (:tbsaunde)
	Comment 4 • 9 years ago

(In reply to Jim Mathies [:jimm] from comment #3)
> (In reply to Trevor Saunders (:tbsaunde) from comment #2)
> > It  seems reasonably possible this is the same issue as bug 1189277, so I
> > think it probably makes sense to see what happens here when builds with that
> > fixed go out.
> 
> These are still showing up, but in much lower numbers.

I see BindChildDoc is also still showing up a little?  I think I might know one cause, but test cases would be very helpful.