Open Bug 2008519 Opened 4 months ago Updated 3 months ago

startup Crash in [@ libwidevinecdm.dylib]

Categories

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

Desktop
macOS
defect

Tracking

()

Tracking Status
firefox146 --- wontfix
firefox147 - fix-optional
firefox148 --- fix-optional

People

(Reporter: aryx, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash)

Crash Data

This macOS crash signature turned more frequent with Firefox 146.0.x. The stack of the reports checked are not symbolized at the top.

[Tracking Requested - why for this release]:

Crash report: https://crash-stats.mozilla.org/report/index/8272e89e-9f53-41eb-ba34-795d00260104

Reason:

EXC_GUARD / GUARD_TYPE_NONE

Top 5 frames:

0  libwidevinecdm.dylib  libwidevinecdm.dylib@0x2ad95a
1  libwidevinecdm.dylib  libwidevinecdm.dylib@0x2d07a9
2  libwidevinecdm.dylib  libwidevinecdm.dylib@0x61eff7
3  libsystem_pthread.dylib  _pthread_start
4  libsystem_pthread.dylib  thread_start

This happens seems to happen exclusively for Mac OSX 13 users. It seems like a sandbox issue where it tries to access something it doesn't have permission to?

Severity: -- → S3
OS: Unspecified → macOS
Hardware: Unspecified → Desktop

I've asked QA in our Widevine update channel to test on a Mac with OSX 13 to see whether this impacts all users or just a subset. There doesn't seem to be any pattern of some particular streaming service -- they are all hitting this.

We tried to reproduce the crash with two machines with macOS 13, on Firefox 146.0.1 accessing Netflix, Amazon Prime, Disney+ videos but we were unable to get the widevine crash mentioned in the bug.
We also set MOZ_DISABLE_GMP_SANDBOX=1 environment variable, but widevine not crashed.
Then we set layers.gpu-process.enabled = false and security.sandbox.gpu.level = 0, we think it is related to the sandbox and that's why we tried this configuration, but widevine not crashed in this case either.

Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.