1673565 - Crash in [@ IPCError-browser | ShutDownKill | mozilla::SyncRunnable::DispatchToThread]

Status: RESOLVED FIXED

(Core :: Audio/Video: Playback, defect)

Description

[Gabriele Svelto [:gsvelto]]

Crash report: https://crash-stats.mozilla.org/report/index/6925c30a-4d6b-47fc-afaa-0579a0201027

Reason: EXCEPTION_BREAKPOINT

Top 10 frames of crashing thread:

0 ntdll.dll NtWaitForAlertByThreadId 
1 ntdll.dll RtlSleepConditionVariableSRW 
2 kernelbase.dll SleepConditionVariableSRW 
3 mozglue.dll mozilla::detail::ConditionVariableImpl::wait mozglue/misc/ConditionVariable_windows.cpp:50
4 xul.dll mozilla::SyncRunnable::DispatchToThread xpcom/threads/SyncRunnable.h:71
5 xul.dll static mozilla::RemoteDecoderManagerChild::Supports dom/media/ipc/RemoteDecoderManagerChild.cpp:216
6 xul.dll mozilla::RemoteDecoderModule::Supports const dom/media/ipc/RemoteDecoderModule.cpp:57
7 xul.dll mozilla::PDMFactory::Supports const dom/media/platforms/PDMFactory.cpp:368
8 xul.dll static mozilla::MP4Decoder::IsSupportedType dom/media/mp4/MP4Decoder.cpp:174
9 xul.dll mozilla::CanHandleMediaType dom/media/DecoderTraits.cpp:194

This appears to be a deadlock during content process shutdown. The main thread dispatched a sync runnable to the manager thread. In the minidump the manager thread has id 17, if you look at its stack you'll notice that it's inside a runnable probably here or here because it's sending a synchronous IPC message to the parent.

In either case that message will never be answered, because the parent has already sent the shutdown IPC message to this content process. So this content process is stuck in that sync IPC call, and gets eventually killed after a timeout.

Comment 1

[Jean-Yves Avenard [:jya]]

Will be fixed with bug 1674043

Comment 2

[Bryce Seager van Dyk [:bryce] (he/him) - Not reading bugmail]

Setting severity to align with bug 1674043, will keep an eye on this to ensure rate drops off as expected once we land code in other bug.

Comment 3

[Jim Mathies [:jimm]]

Hey Jya, can we close this out?

Comment 4

[Jean-Yves Avenard [:jya]]

this will have been fixed by bug 1674043