Open ROBERT-MCDOWELL opened 2 years ago
According to the logs the buffer is provisioned. The stall is likely reported because the player is observing that currentTime has not changed for more than a certain threshold.
ok so does it mean the player is too much redundant?
hls.js:7631 [warn] > Playback stalling at @12.996104 due to low buffer ({"len":87.012239,"start":0.023222,"end":100.008343})
_reportStall @ hls.js:7631
poll @ hls.js:7559
checkBuffer @ hls.js:10425
This means that the stall event was fired at 12.9s of playback with 87 seconds of buffer available by checkBuffer
. It would only do this if the browser you are running failed to update currentTime
between multiple checks for a certain period. Yes it is too redundant and should rely more prominently on waiting
and canplay
events and only fallback to currentTime
observation when these events do not fire or the playback is not advancing on or near a buffer gap.
I've observed similar behavior in Chrome 107-108. It might be related to JavaScript throttling or some other internal issue. Restarting Chrome clears things up.
@robwalch thanks for the clarification. weird it's also happening on last chrome versions.... did not know there is such kind of throttle for javascript.... is it also possible that the GPU / CPU busy for something else has not enough speed/time to interpret the jS?
it's possible
Related to #4884
do you think a compromise can be done from the code? I close the issue?
What version of Hls.js are you using?
LAST
What browser (including version) are you using?
All browsers
What OS (including version) are you using?
All OS
Test stream
https://hls-js-bbdf933d-da48-407d-aaf3-68cc4ee058e7.netlify.app/demo/?src=https%3A%2F%2Ftest-streams.mux.dev%2Fx36xhzz%2Fx36xhzz.m3u8&demoConfig=eyJlbmFibGVTdHJlYW1pbmciOnRydWUsImF1dG9SZWNvdmVyRXJyb3IiOnRydWUsInN0b3BPblN0YWxsIjpmYWxzZSwiZHVtcGZNUDQiOmZhbHNlLCJsZXZlbENhcHBpbmciOi0xLCJsaW1pdE1ldHJpY3MiOi0xfQ==
Configuration
Additional player setup steps
No response
Checklist
Steps to reproduce
Play demo without changes
....
Expected behaviour
buffer must be filled better
What actually happened?
I tested the demo with the first video on the list and the rest untouched and I get bufferStalledError on all browsers last vevrsion on a 100Mb/s line where I everyday watch multiple simultaneous HD streaming from YT any clue why I get so many buffer error?
Console output
Chrome media internals output
No response