"Infinite spinner" for live content (currentTime ouside of buffered start) #3482
Labels
priority: P2
Smaller impact or easy workaround
status: archived
Archived and locked; will not be updated
type: bug
Something isn't working correctly
Milestone
Have you read the FAQ and checked for duplicate open issues?
Yes
What version of Shaka Player are you using?
3.1.1
Can you reproduce the issue with our latest release version?
N/A
Can you reproduce the issue with the latest code from
master
?Not tested (yet) due to time constraints
Are you using the demo app or your own custom app?
Both.
If custom app, can you reproduce the issue using our demo app?
Yes
What browser and OS are you using?
Linux, Mac, Windows, Firefox, Chrome
What are the manifest and license server URIs?
Sent via email.
What configuration are you using? What is the output of
player.getConfiguration()
?Full config (minus keySystems, since test stream is drm free)
What did you do?
We discovered this when testing HLS streams that do not support
range
headers, causing CORS failures on the first few requests. With retry parameters set for manifest requests, this results in shaka getting stuck in a state where the stream never starts playing.Without retry parameters set, the failed
range
attemps happen fast enough for the stream to work as intended.We can fix this particular case by setting
useFullSegmentsForStartTime: true
which prevents therange
requests from occurring, but I believe the root issue still persists in case the manifest fetch would fail for some other reason (e.g. a temporary network error), combined with retries.What did you expect to happen?
The live stream starts playing.
What actually happened?
The live stream does not start playing.
Player is stuck with an infinite spinner, with
currentTime
always just outside of buffered start:Modifying
video.currentTime
will make the stream start playing.Pressing pause/play triggers a jump large enough to make the stream start playing.
The text was updated successfully, but these errors were encountered: