Open Bug 1625844 Opened 7 months ago Updated 6 months ago

Crash in [@ IPCError-browser | ShutDownKill | mozilla::CanCreateMFTDecoder]


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





(Reporter: gsvelto, Assigned: bryce)



(Keywords: crash, Whiteboard: [media-crash])

Crash Data

This bug is for crash report bp-ffab8cee-f5f3-4ceb-bd0a-b31670200329.

Top 10 frames of crashing thread:

0 ntdll.dll NtWaitForSingleObject 
1 kernelbase.dll WaitForSingleObjectEx 
2 xul.dll mozilla::CanCreateMFTDecoder dom/media/platforms/wmf/WMFDecoderModule.cpp:63
3 xul.dll static mozilla::WMFDecoderModule::HasH264 dom/media/platforms/wmf/WMFDecoderModule.cpp:170
4 xul.dll mozilla::WMFDecoderModule::Supports const dom/media/platforms/wmf/WMFDecoderModule.cpp:209
5 xul.dll mozilla::PDMFactory::GetDecoder const dom/media/platforms/PDMFactory.cpp:441
6 xul.dll mozilla::PDMFactory::Supports const dom/media/platforms/PDMFactory.cpp:330
7 xul.dll static mozilla::MP4Decoder::IsSupportedType dom/media/mp4/MP4Decoder.cpp:175
8 xul.dll static mozilla::DecoderTraits::IsSupportedType dom/media/DecoderTraits.cpp:295
9 xul.dll static mozilla::ChannelMediaDecoder::Create dom/media/ChannelMediaDecoder.cpp:177

These are from content process stuck creating a decoder. The vast majority of the reports don't have the IPCShutdownState annotation set which means they didn't respond to the content shutdown message at all for five seconds and didn't even begin to shut down.

There's lots of inlining going on but I believe that the call we're stuck in is this one.

Assignee: nobody → bvandyk
Priority: -- → P3
Whiteboard: [media-crash]

Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is P3 (Backlog,) indicating it has been triaged, the bug's Severity is being updated to S3 (normal.)

Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.