Network errors cause jump past end of buffer

[nathanmarlor]

What version of Hls.js are you using?

1.1.5

What browser (including version) are you using?

101.0.4951.64 (Official Build) (x86_64)

What OS (including version) are you using?

macOS Catalina

Test stream

On request

Configuration

{
  "debug": true,
  "enableWorker": true,
  "lowLatencyMode": true,
  "backBufferLength": 60
}

Additional player setup steps

No response

Checklist

• The issue observed is not already reported by searching on Github under https://github.com/video-dev/hls.js/issues
• The issue occurs in the stable client (latest release) on https://hls-js.netlify.com/demo and not just on my page
• The issue occurs in the latest client (main branch) on https://hls-js-dev.netlify.com/demo and not just on my page
• The stream has correct Access-Control-Allow-Origin headers (CORS)
• There are no network errors such as 404s in the browser console when trying to play the stream

Steps to reproduce

1. Allow stream to play
2. Network error occurs (404 on level 0 playlist)

Expected behaviour

HLS should continue to fill it's buffers ahead of skipping forwards at the end of the sliding window.

What actually happened?

HLS buffered the next segment but not past, meaning the skip forwards jumped over the available buffer. Playback does not resume following this.

Recording of issue on demo environment: https://youtu.be/bmLTw2WxyW0

Console output

https://pastebin.com/zKntA46Y

Chrome media internals output

https://pastebin.com/Y4eCk2vm

[robwalch]

Please see if #5122 resolves this issue and include a sample stream or codec and timecode details that may help to reproduce or explain some of the behavior described.

[robwalch]

Closing as we haven't received a sample to reproduce the issue.

See possibly related issues:

• Chrome does not recognise old keyframes (LL-HLS issue) #3596