Playback of widevine assets (encrypted from the start) with persistent license state can fail to playback in chrome when the licensor takes some time to respond
Reported by
chris.he...@gmail.com,
Jun 13 2016
|
||||||
Issue description
Chrome Version : 51.0.2704.79.m
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari: n/a
Firefox: n/a
IE: n/a
What steps will reproduce the problem?
(1) With the persistent state enabled in Widevine.
(2) Playback a test movie that is encrypted from the start (many have the first segment unencrypted)
(3) Have the licensor take some time to respond (this can be random based on the windows machine but 0.7 to 0.9 seconds seems to do it)
(4) It will intermittently not play back with a no key error in chrome://media-internals/ (attached)
(5) When this happens the eme logger extension also show it fire the KeyStatusesChangeEvent before the session promise resolves (attached)
What is the expected result?
It should play back fine.
What happens instead?
A no key error occurs in chrome://media-internals/ and play back does not work
Please provide any additional information below. Attach a screenshot if
possible.
I have created a branch of the latest shaka player so this bug is more visible here https://github.com/chris-heathwood-piksel/shaka-player/tree/windows_persistent_error :
1. Check out the branch
2. Run ./build/all.py
3. Host the root of the folder
4. Playback "Tears of Steel (Widevine)"
The "var windowsBrokenTime = 786" is a magic number based on my windows machine but it does break on the three machines I have tested it on.
,
Jul 1 2016
Adding proper label for someone from the respective team to have a look at this and help in further debugging.
,
Jul 12 2016
,
Jul 14 2016
,
Jul 14 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 17 2017
stale bug for > 1 year. close it with StaleClosed label. Please feel free to reactivate and assign appropriately if you think it's worth to keep. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by kavvaru@chromium.org
, Jun 14 2016