Closed Bug 1523304 Opened 7 years ago Closed 7 years ago

Crash in libwidevinecdm.dylib@0x1e2af3

Categories

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

Product:
Core
Component:
Audio/Video: Playback
Platform:
Unspecified
macOS
Type:
defect

Tracking

()

Status:
RESOLVED INVALID
Tracking Flags:
Tracking Status
firefox65 --- unaffected
firefox66 --- wontfix
firefox67 --- affected

People

(Reporter: marcia, Unassigned)

Details

(Keywords: crash, regression)

Crash Data

This bug is for crash report bp-c3829706-0e19-4e3b-abd2-4252f0190127.

Seen while looking at nightly crash stats - 11 crashes/2 installs so far: https://bit.ly/2CS1tlx

plugin (web) WidevineCdm Version: 4.10.1196.0 Filename: widevinecdm

Top 10 frames of crashing thread:

0  @0x288 
1 libwidevinecdm.dylib libwidevinecdm.dylib@0x1e2af3 
2 libwidevinecdm.dylib libwidevinecdm.dylib@0xc0e16 
3 libwidevinecdm.dylib libwidevinecdm.dylib@0xb6370 
4 libwidevinecdm.dylib libwidevinecdm.dylib@0x93a67 
5 libwidevinecdm.dylib libwidevinecdm.dylib@0x93b2d 
6 libwidevinecdm.dylib libwidevinecdm.dylib@0x93a3b 
7 libwidevinecdm.dylib libwidevinecdm.dylib@0x93b2d 
8 libwidevinecdm.dylib libwidevinecdm.dylib@0x93a3b 
9 libwidevinecdm.dylib libwidevinecdm.dylib@0xe5ff8

The nightly 66 crashes are all on 10.14.0 18A391 which is the original Mojave release. There are also two crashes in this signature, one on 64.0 and one running 64.0.2.

Hi, Bryce,
Is this something you can take a look?
Thank you!

Flags: needinfo?(bvandyk)
Priority: -- → P2

The code we have to interact with the CDM here hasn't changed in central recently. I've reached out to Widevine to see if they have any knowledge of things changing on their end that could cause this issue.

Flags: needinfo?(bvandyk)

After discussion it appears this is not a Firefox specific issue, and thus not one we can fix. I think our best course of action is to track this and escalate with Widevine should crash rates spike. We expect to ship a new CDM in the current cycle (or the following cycle at the latest), in which case I would hope to see this resolved.

I marked it wontfix for 66 and affected for 67 so that we can track it for the next release as per Bryce's suggestion

status-firefox66: affected → wontfix
status-firefox67: --- → affected

There are no crashes in 65 or 65.0.1 release and no current crashes in 66 or 67. Suggest based on no volume that we just close this one out.

Closed per comment 6.

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