Closed Bug 1278432 Opened 6 years ago Closed 4 years ago

Crash in IPCError-browser | (msgtype=0xD80005,name=???) Unknown message: not processed


(Core :: IPC, defect, P3)

Windows 10



Tracking Status
e10s + ---
firefox50 --- affected


(Reporter: ting, Unassigned)


(Keywords: crash)

Crash Data

This bug was filed from the Socorro interface and is 
report bp-e6b2430d-f288-4c14-87d5-8beef2160606.

#3 in Nightly 20160605030215, 16 crashes from 4 installations.

The first observation was from build 20160603030242, 3 crashes from 1 installations.
All the crashes were from content process, and the uptime is <1 minute. The stack from minidump of crash e6f20895-7de5-4f0e-a016-e269f2160606:

  ntdll.dll!NtWaitForSingleObject()	Unknown
  KERNELBASE.dll!WaitForSingleObjectEx()	Unknown
  nss3.dll!PR_WaitCondVar(PRCondVar * cvar, unsigned int timeout) Line 525	C
  xul.dll!mozilla::CondVar::Wait(unsigned int aInterval) Line 79	C++
  xul.dll!mozilla::ipc::MessageChannel::WaitForSyncNotify(bool aHandleWindowsMessages) Line 1084	C++
  xul.dll!mozilla::ipc::MessageChannel::Send(IPC::Message * aMsg, IPC::Message * aReply) Line 1185	C++
  xul.dll!mozilla::dom::PScreenManagerChild::SendGetPrimaryScreen(mozilla::dom::ScreenDetails * screen, bool * success) Line 191	C++
  xul.dll!nsScreenManagerProxy::GetPrimaryScreen(nsIScreen * * outScreen) Line 69	C++
  xul.dll!gfxPlatform::PopulateScreenInfo() Line 1227	C++
  xul.dll!gfxPlatform::Init() Line 685	C++
  xul.dll!gfxPlatform::GetPlatform() Line 517	C++
  xul.dll!mozilla::dom::ContentProcess::Init() Line 128	C++
  xul.dll!XRE_InitChildProcess(int aArgc, char * * aArgv, const XREChildData * aChildData) Line 629	C++
  plugin-container.exe!NS_internal_main(int argc, char * * argv) Line 11	C++
  plugin-container.exe!wmain(int argc, wchar_t * * argv) Line 123	C++
  plugin-container.exe!__scrt_common_main_seh() Line 255	C++
  kernel32.dll!BaseThreadInitThunk()	Unknown
  ntdll.dll!RtlUserThreadStart()	Unknown
Actually it's the parent received the message 0xD80005 from the child, treated it as an unknown message and killed the child. Probably this is another side effect from "update" that child process is sending the message with updated type integer, but parent is still running the old binary and expects a different number.
Andrew McCreight noted that there were a few bugs recently reported that could possibly be explained by the child and parent processes being from different Firefox version ...
tracking-e10s: --- → ?
Priority: -- → P3
Closing because no crash reported since 12 weeks.
Closed: 4 years ago
Resolution: --- → WONTFIX
Closing because no crash reported since 12 weeks.
You need to log in before you can comment on or make changes to this bug.