Closed Bug 1647275 Opened 2 years ago Closed 7 months ago

Crash in [@ IPCError-browser | ShutDownKill | MsgWaitForMultipleObjectsEx | CCliModalLoop::BlockFn]

Categories

(Core :: Graphics, defect)

Unspecified
Windows
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: gsvelto, Unassigned)

Details

(Keywords: crash)

Crash Data

This bug is for crash report bp-fd2a2cbb-4acc-44a7-b91a-dd77d0200622.

Top 10 frames of crashing thread:

0 ntdll.dll NtWaitForMultipleObjects 
1 kernelbase.dll WaitForMultipleObjectsEx 
2 user32.dll MsgWaitForMultipleObjectsEx 
3 combase.dll CCliModalLoop::BlockFn d:\9147\com\combase\dcomrem\callctrl.cxx:1571
4 combase.dll ClassicSTAThreadWaitForHandles d:\9147\com\combase\dcomrem\classicsta.cpp:46
5 combase.dll CoWaitForMultipleHandles d:\9147\com\combase\dcomrem\sync.cxx:120
6 xul.dll mozilla::ipc::MessageChannel::WaitForSyncNotifyWithA11yReentry ipc/glue/WindowsMessageLoop.cpp:892
7 xul.dll mozilla::ipc::MessageChannel::Send ipc/glue/MessageChannel.cpp:1532
8 xul.dll mozilla::ipc::IProtocol::ChannelSend ipc/glue/ProtocolUtils.cpp:477
9 xul.dll mozilla::dom::PContentChild::SendGetGraphicsDeviceInitData ipc/ipdl/PContentChild.cpp:5026

This is a content process shutdown hang that seems triggered by the following scenario:

  • The child process receives a ReinitRendering IPC message
  • While the child is executing the IPC message the main process decides to shut it down
  • While executing ReinitRendering the child got to this point where it's trying to execute a synchronous IPC call (GetGraphicsDeviceInitData) (see here)
  • Since the main process has decided to shut it down it won't respond, leaving the child process unable to proceed and unable to respond to the shutdown IPC message. The main process will then force-kill the content process leading to these reports

Probably the only sane way to fix this is the remove the sync call. That might prove tricky...

Severity: -- → S3

Closing because no crashes reported for 12 weeks.

Status: NEW → RESOLVED
Closed: 7 months ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.