shaka-player: Shaka 3 rebuffers indefinitely on VDMS dash live stream after 3-5 minutes (works fine in shaka 2.x)

Have you read the FAQ and checked for duplicate open issues? Yes

What version of Shaka Player are you using? 3.0.8

Can you reproduce the issue with our latest release version? Yes

Can you reproduce the issue with the latest code from master? Yes - But I cannot reproduce it in shaka 2.4/2.5

Are you using the demo app or your own custom app? Demo App

If custom app, can you reproduce the issue using our demo app? NA

What browser and OS are you using? Chrome on macos

For embedded devices (smart TVs, etc.), what model and firmware version are you using? NA

What are the manifest and license server URIs?

Manifest: https://content-ausw7.uplynk.com/channel/b965d55496414804891dde9c96928ffb.mpd?rays=abcd&delay=30 License: https://content.uplynk.com/wv

What did you do?

Just play back any Verizon Media Dash Live stream for for 5 minutes or so and you will get infinite rebuffering

What did you expect to happen? Playback without infinite rebuffering

What actually happened?

I recorded a little demo video that guides you through what is happening:

https://content.uplynk.com/player5/PjpqgfaCDjuJxkQHgrBvXsa.html

Basically after ~ 3 minutes shaka starts redownloading all slices after a certain slice after ever manifest update it gets to a point where it is downloading more than a dozen slices after each manifest refresh and then it starts infinitely buffering.

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 19 (16 by maintainers)

Commits related to this issue

Most upvoted comments

The fix for the master branch key rotation issue has been merged. Everything should be working in the nightly build after tonight.

The fix for the redownloading issue has been cherry-picked, but not yet pushed to v3.0.x until I can verify that all (29) cherry-picks for this branch so far are correct and passing tests. I have a few test failures to investigate before I can push those changes to that branch, but the fix will be out in v3.0.11 shortly afterward.

  • What change in master fixes the re-downloading issue? It should be cherry-picked to v3.0.x.

I performed a git bisect to track down the fix in master that is still needed in v3.0.x. At each step, I had to manually add back the filter() call I mentioned that was removed in acfa1a8. This process revealed that the redownloading issue was fixed in 7e50866bb539ddd7e70ed6d6c245793b353262a6. We will cherry-pick this to v3.0.x, so this should fix the issue in v3.0.11.