Crash report: https://crash-stats.mozilla.org/report/index/75379d0e-d048-4dc3-9d41-849380230427

MOZ_CRASH Reason: Cannot load plugin as library -5977 126

Top 10 frames of crashing thread:

0  xul.dll  MOZ_Crash  mfbt/Assertions.h:261
0  xul.dll  mozilla::gmp::GMPLoader::Load  dom/media/gmp/GMPLoader.cpp:121
1  xul.dll  mozilla::gmp::GMPChild::RecvStartPlugin  dom/media/gmp/GMPChild.cpp:484
2  xul.dll  mozilla::gmp::PGMPChild::OnMessageReceived  ipc/ipdl/PGMPChild.cpp:787
3  xul.dll  mozilla::ipc::MessageChannel::DispatchSyncMessage  ipc/glue/MessageChannel.cpp:1767
3  xul.dll  mozilla::ipc::MessageChannel::DispatchMessage  ipc/glue/MessageChannel.cpp:1723
4  xul.dll  mozilla::ipc::MessageChannel::RunMessage  ipc/glue/MessageChannel.cpp:1525
5  xul.dll  mozilla::ipc::MessageChannel::MessageTask::Run  ipc/glue/MessageChannel.cpp:1623
6  xul.dll  MessageLoop::RunTask  ipc/chromium/src/base/message_loop.cc:492
6  xul.dll  MessageLoop::DeferOrRunPendingTask  ipc/chromium/src/base/message_loop.cc:501

About half of the crashes have -5977 126 and about half have -5977 4581.

Yes this is a signature morph from the previous ProcessingError crashes as a result of my investigations/changes for more info.

The bug is linked to a topcrash signature, which matches the following criterion:

• Top 5 desktop browser crashes on Linux on release

:aosmond, could you consider increasing the severity of this top-crash bug?

For more information, please visit BugBot documentation.

Based on the topcrash criteria, the crash signature linked to this bug is not a topcrash signature anymore.

For more information, please visit BugBot documentation.

Sorry for removing the keyword earlier but there is a recent change in the ranking, so the bug is again linked to a topcrash signature, which matches the following criterion:

• Top 20 desktop browser crashes on release

For more information, please visit BugBot documentation.

Based on the topcrash criteria, the crash signature linked to this bug is not a topcrash signature anymore.

For more information, please visit BugBot documentation.

Sorry for removing the keyword earlier but there is a recent change in the ranking, so the bug is again linked to a topcrash signature, which matches the following criterion:

• Top 10 desktop browser crashes on nightly

For more information, please visit BugBot documentation.

I stumbled upon this during crash triage. The most frequent raw crash reason now appears to be Cannot load plugin as library -5977 998 however this might be caused by a few users sending a lot of crash reports each and so not really representative of the crash distribution.

Based on the topcrash criteria, the crash signature linked to this bug is not a topcrash signature anymore.

For more information, please visit BugBot documentation.

This can happen when the user gets a stale xml manifest that points to an outdated version of the widevine plugin, or in cases where the update for a new cdm has been failing for a long time, such that Firefox attempts to load a cdm that's out of date. Reproduced by QA using a stage server that had a stale config in it.