-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
[buffer-controller]: Error encountered while trying to append to the video SourceBuffer #4506
Comments
@Andyczc thanks for surfacing. Do you have a playlist available that can be used on the demo page to reproduce this issue? |
+1 with the same issue here. Console log is almost the same - no reason to post the duplicate here. {
maxBufferSize: 320 * 1000 * 1000,
} If you set Also it does not look like the stream matters. |
@dylanjha My guesses of the possibilities.
|
Experiencing this issue on the latest build when scrubbing using Wowza nDVR. |
Hi @invalidtask, Please file a new issue with a sample stream and steps to the reproduce. And, be sure to indicate the version of the build in your bug report. |
Sounds like the issue is related to the content, not the buffer size. Cannot reproduce or further triage without a sample stream that can be used to reproduce the issue. |
Same error here. If ever this could help:
|
Hi @lnstadrum, What happens when attempting to reproduce the issue against dev with #5731 here: https://bugfix-fix-media-source-clos.hls-js-4zn.pages.dev/demo/ Do you have a sample you could share? Can you please share the Android and Chrome versions you used to reproduce the issue on Pixel 5? Are there error messages preceding the one(s) that you shared? This error message would only be displayed after the media element is in an error state and/or video/MediaSource has been detached and is no longer usable. So it is likely that a decode error occurred before this error, which doesn't tell us much. The branch above should handle these kind of issues better so that the player does not try to access or append media after the MediaSource has been closed because of another error.
|
I had a similar issue, but my problem was the buffer size itself. Looks like the browser has some limitations on memory allocated for a single tab, so the player can't use more than that. If the buffer is too big, there are just not enough memory for it. I've been playing with different streams - the lower the quality of the stream, the longer buffer length can be achieved (in seconds). |
Hi @write2art,
If that was the case we should be seeing The full logs originally submitted follow a PIPELINE_ERROR_DECODE which suggests invalid media was appended putting the HTMLMediaElement and the browser MediaSource into an error state. A Please file new issues with full logs and steps to reproduce so that we can see if your particular path to getting a |
In my condition, I'm trying to play video in chromium runtime of VSCode (for theme personalization, DON'T LAUGH AT ME): And finally I found that it seems that the errors disappeared after I removed the audio from the video file. FYI. https://superuser.com/questions/268985/remove-audio-from-video-file-with-ffmpeg |
Closing as a sample has not been provided and addition comments reproducing the same error but for different reasons should be filed as new issues. |
What version of Hls.js are you using?
1.1.4-0.canary.8150
What browser (including version) are you using?
Chrome Version 93.0.4577.82 (Official Build) (x86_64)
What OS (including version) are you using?
MAC OS (and other)
Test stream
No response
Configuration
Additional player setup steps
No response
Checklist
Steps to reproduce
2.Waiting to play to 01:19:26
Expected behaviour
Handling exceptions
What actually happened?
Console reports error, player stuck
Console output
Chrome media internals output
The text was updated successfully, but these errors were encountered: