Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Playback stuck after BUFFER_FULL_ERROR #3565

Closed
lp-contentplus opened this issue Mar 4, 2021 · 4 comments
Closed

Playback stuck after BUFFER_FULL_ERROR #3565

lp-contentplus opened this issue Mar 4, 2021 · 4 comments
Labels

Comments

@lp-contentplus
Copy link

lp-contentplus commented Mar 4, 2021

What version of Hls.js are you using?

1.0.0-rc2

What browser and OS are you using?

Chrome 88, Linux

Test stream:

https://static.epodreczniki.pl/editor/resized/v2/hls/storage/resource/R1Hv5FP6meiKo/14t0VjZSpq4LDx5uy14u4Fvie5CVVNNt.mp4/index.m3u8

{
"debug": true,
"enableWorker": true,
"liveBackBufferLength": 900
}

Steps to reproduce

  • Play stream, allow fill buffer.
  • BUFFER_FULL_ERROR triggers
[log] > main stream-controller: IDLE->FRAG_LOADING
logger.js:40 [error] > error while trying to append buffer:Failed to execute 'appendBuffer' on 'SourceBuffer': The SourceBuffer is full, and cannot free space to append additional buffers.
logger.js:40 [warn] > AudioStreamController: reduce max buffer length to 300s
logger.js:40 [log] > audio stream:PARSED->IDLE
main.js:568 Error event: {type: "mediaError", parent: "audio", details: "bufferFullError", fatal: false}
  • playback stucks when current time hits end of buffered range (you can seek, to get to this point)
[warn] > Playback stalling at @543.868178 due to low buffer (buffer=0.07213800000010906)
Error event: {type: "mediaError", details: "bufferStalledError", fatal: false, buffer: 0.07213800000010906}

It's seems that more parts loads when getting close to end of buffered range, but player does not use them

@robwalch
Copy link
Collaborator

robwalch commented Mar 4, 2021

Hi @lp-contentplus,

Thanks for the bug report. Have you tested or are you able to reproduce on any other platforms?

Can you provide more information about the device, OS, and browser (model, physical memory, app allocated memory)?

Have you tried using a shorter back-buffer length (since the error occurs at ~500s, but you've set liveBackBufferLength to 900)?

@robwalch robwalch added the Needs Triage If there is a suspected stream issue, apply this label to triage if it is something we should fix. label Mar 4, 2021
@lp-contentplus
Copy link
Author

Thanks for the bug report. Have you tested or are you able to reproduce on any other platforms?

Can you provide more information about the device, OS, and browser (model, physical memory, app allocated memory)?

Bug occurs only on chrome. All operating systems (also MacOS, Windows 10). Several persons reported same issue.

Have you tried using a shorter back-buffer length (since the error occurs at ~500s, but you've set liveBackBufferLength to 900)?

liveBackBufferLength: 900 was just default playground setting. I've tried with backBufferLength: 90 and it's still occurs.

Currently we are deployed player with maxMaxBufferLength: 180. It's just prevents BUFFER_FULL_ERROR.
I'm afraid that limit may still be hit with higher video quality.

@shnjp
Copy link

shnjp commented Apr 23, 2021

I encountered a similar problem.
What happens if you make maxBufferSize/maxBufferLength smaller?
That worked in our case.

Perhaps hls.js is adding an amount of data that overflows the SourceBuffer, and I suspect that reduceMaxBufferLength() is not working properly.

@robwalch robwalch added Stale and removed Needs Triage If there is a suspected stream issue, apply this label to triage if it is something we should fix. labels Aug 17, 2022
@robwalch
Copy link
Collaborator

Changes in #3774, #3914, and #4686 (v1.0.1-v1.2.0) should have resolved this issue. If you are still experiencing something similar using the latest release, please submit a new bug report.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants