1505563 - [Widevine] Missing decryption key after succesful license request when using persistentStateRequired

Status: RESOLVED FIXED

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

Description

[juan.pablo.franco]

Attachment: Firefox Widevine Error.png

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36

Steps to reproduce:

Play a Widevine DRM protected video multiple times. Set the persistentStateRequired option to true in order to allow device registration.


Actual results:

Playback fails randomly, about 1 out of 40 times (i.e. if you refresh the page multiple times). When playback fails, the license request returns with a 200 status, but the browser fails to decrypt segments with the newly acquired key. You can see the error message on the attached screenshot.


Expected results:

Playback should succeed every time.

IMPORTANT:

This has been identified as a Widevine CDM issue and was originally reported here:

https://github.com/google/shaka-player/issues/1554

I'm mostly filing this ticket in order to keep track of the fact that this is also affecting Firefox and to hopefully get an ETA on when this Widevine CDM update will be included in Firefox.

Comment 1

[ovidiu boca[:Ovidiu]]

Hi Juan,
I want to reproduce this issue but I can't set the persistentStateRequired option. Where can I find that option, in about:config? Also if you can share the video for reproducing this issue it will be great, if not please tell me if you can reproduce the issue using a video from here: https://shaka-player-demo.appspot.com/demo/#asset=https://content.uplynk.com/224ac8717e714b68831997ab6cea4015.mpd;lang=en-US;build=uncompiled

Bryce, do you know something about this issue?

Comment 2

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

Thanks for filing this bug, Juan.

Based on details from the github issue in comment #0, as well as the note at the end of comment #0, it sounds like this is (solely?) a CDM problem. The Chrome bug is closed in order to share the video used to repro, but details include the following, which looks to be quoted from the Chrome bug:

> We missed the M71 branch cut to land the CDM with this change. This change will be in M72 Chrome.

Chrome 72 appears to be using CDM 4.10.1224.5, though this may change before it rides to release. This CDM is not available for us to test yet, but once it is we should be able to get it into nightly relatively quickly -- typically in the same cycle it's made available, though the timing of Chrome 72 may mean we need to do it in the following cycle.

Chrome 72 is set to branch on the 29th of November. Provided the CDM is stabilized around then and we can start testing in nightly, I would expect us to ship it for Firefox 67.

Comment 3

[juan.pablo.franco]

Sorry @Ovidiu, I should've clarified that persistentStateRequired is set on the video player configuration. In the case of Shaka, this can be set using the advanced DRM configuration properties: https://shaka-player-demo.appspot.com/docs/api/shakaExtern.html#.AdvancedDrmConfiguration

Unfortunately I don't have a public domain asset that manifests the issue at the moment. I will check to see if one of Shaka demo assets manifests the issue and I'll let you know if this is the case.

@Bryce correct, the issue appears to be solely at the CDM level, or at least that's what I understood from the Google devs' responses. Thanks for sharing the timeline for CDM adoption.

Comment 4

[stephen.p.paddon]

Any update on this? Bryce mentioned expecting it to be updated with Firefox 67, but given recent activities around updating the Widevine CDM, I suspect the CDM might be updated sooner than that release?

Comment 5

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

Stephen, are you seeing the issue with any public assets we could use to reproduce? What OS are you seeing the issue on, and what version of Firefox?

We've bumped the version of the CDM we're using since this bug was created, but had to revert the Windows CDM due to performance issues. So it would be useful to know if you're seeing the problem only on Windows.

We're currently awaiting another update of the CDM from Widevine, which we expect to be made available to us during March.

Comment 6

[stephen.p.paddon]

@bryce - we have permission to share the asset with devs for troubleshooting purposes so long as the url is not publicly accessible. If that's an option, please advise on method of getting the asset to you privately.

Comment 7

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

If you can send the URL and any required login details to the email associated with my bugzilla profile I can investigate.

Comment 8

[Tony]

@Bryce is there an update on this. Do you know when the CDM in Firefox will be updated to fix this issue?

Comment 9

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

(In reply to Tony from comment #8)

@Bryce is there an update on this. Do you know when the CDM in Firefox will be updated to fix this issue?

Since the bug was first reported the CDM has been updated and we'd expect to see this fixed in current releases if this is a CDM specific issue. I take it you're still seeing the issue? Would it be possible to provide a link to reproduce -- you can send login details to my mozilla email if you'd prefer them to not be on a public tracker.

Comment 10

[Tony]

Hi Bryce, my understanding is that the issue was fixed in Chrome 72 which had the CDM version of 4.10.1303.2. When I checked the Firefox nightly build 69.0a1 (2019-06-14), it was still using CDM version 4.10.1196.0.

My assumption is the issue would be fixed when Firefox has upgraded to CDM version 4.10.1303.2 or above.

Comment 11

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

(In reply to Tony from comment #10)

Hi Bryce, my understanding is that the issue was fixed in Chrome 72 which had the CDM version of 4.10.1303.2. When I checked the Firefox nightly build 69.0a1 (2019-06-14), it was still using CDM version 4.10.1196.0.

My assumption is the issue would be fixed when Firefox has upgraded to CDM version 4.10.1303.2 or above.

My understanding is that it may have been fixed prior to that release, but that's going off the the gh bug. There's mixed reports that it should be fixed by 71, and another saying that it's expected from 72.

It would be useful to know if you're seeing issues (and if it's Windows specific, per comment 5). We're expecting a new CDM to be provided to us in the near future, which I would hope to help with the issue should it be persisting.

Comment 12

[Tony]

Hi Bryce, I can see in the latest Firefox nightly the CDM was upgraded to 4.10.1440.18. This issue is resolved with this version.

Thanks!!

Comment 13

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

(In reply to Tony from comment #12)

Hi Bryce, I can see in the latest Firefox nightly the CDM was upgraded to 4.10.1440.18. This issue is resolved with this version.

Thanks!!

Thanks for verifying that.

With bug 1561693 rolling out to all platforms I'm resolving this.