New issue
Advanced search Search tips

Issue 900844 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Nov 13
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

MediaKeySystemAccess.createMediaKeys dose not work after close a page while playing an encrypted media

Reported by makoto...@gmail.com, Nov 1

Issue description

Steps to reproduce the problem:
1. Open https://shaka-player-demo.appspot.com/demo/
2. Select a WideVine from Asset list
3. Tap Load button
4. Reload this page after the video has started
5. Repeat step 2-4
6. Asset dose not appear on the Asset list
7. Chrome can not play any media even if clear content

What is the expected behavior?
- Chrome can play a media after a page is reloaded or closed while playing a encrypted media

What went wrong?
- MediaKeySystemAccess.createMediaKeys() never respond.
- Chrome can not play anything media even if clear content.
- These problems will be resolved after restart Chrome.

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 70.0.3538.80  Channel: stable
OS Version: 5.1.1
Flash Version: 

- This problem was reproduced on all device I have. (Android 5, 6, 7)
- It was also reproduced with Dash.js. 
  https://reference.dashif.org/dash.js/v2.9.1/samples/dash-if--reference-player/index.html
- I could not reproduce it in Desktop Chrome.
 
mobizen_20181101_140613.mp4
2.9 MB View Download
Components: Internals>Media>Encrypted
Cc: jrumm...@chromium.org
Owner: xhw...@chromium.org
Status: Assigned (was: Unconfirmed)
Labels: FoundIn-70 M-71 Target-71
Cc: -jrumm...@chromium.org xhw...@chromium.org
Owner: jrumm...@chromium.org
Assign to jrummell@. Thanks!
Status: Fixed (was: Assigned)
I can get this to fail with Shaka 2.4.5 on Chrome 70.0.3538.80. However, it works with Chrome beta (71.0.3578.45) and Chrome Canary (72.0.3608.5).

Given that Chrome 70 has shipped, there is nothing we can do. Marking this as Fixed as it is fixed in 71 and later. Please reopen if 71 or later still sees this issue.

Sign in to add a comment