An attempt was made to use an object that is not, or is no longer, usable #5070
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
Comments
This was referenced Mar 8, 2023
theodab
pushed a commit
that referenced
this issue
Mar 9, 2023
This prevents the streaming engine from calling MediaSource.endOfStream when media source's readyState is "closed". It's not valid to close a stream that is already closed. See: https://developer.mozilla.org/en-US/docs/Web/API/MediaSource/endOfStream#exceptions Fixes #5070
joeyparrish
pushed a commit
that referenced
this issue
Apr 26, 2023
This prevents the streaming engine from calling MediaSource.endOfStream when media source's readyState is "closed". It's not valid to close a stream that is already closed. See: https://developer.mozilla.org/en-US/docs/Web/API/MediaSource/endOfStream#exceptions Fixes #5070
joeyparrish
pushed a commit
that referenced
this issue
Apr 26, 2023
This prevents the streaming engine from calling MediaSource.endOfStream when media source's readyState is "closed". It's not valid to close a stream that is already closed. See: https://developer.mozilla.org/en-US/docs/Web/API/MediaSource/endOfStream#exceptions Fixes #5070
joeyparrish
pushed a commit
that referenced
this issue
Apr 26, 2023
This prevents the streaming engine from calling MediaSource.endOfStream when media source's readyState is "closed". It's not valid to close a stream that is already closed. See: https://developer.mozilla.org/en-US/docs/Web/API/MediaSource/endOfStream#exceptions Fixes #5070
joeyparrish
pushed a commit
that referenced
this issue
Apr 26, 2023
This prevents the streaming engine from calling MediaSource.endOfStream when media source's readyState is "closed". It's not valid to close a stream that is already closed. See: https://developer.mozilla.org/en-US/docs/Web/API/MediaSource/endOfStream#exceptions Fixes #5070
github-actions
bot
added
the
status: archived
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Have you read the FAQ and checked for duplicate open issues?
Yes
What version of Shaka Player are you using?
4.3.4
Can you reproduce the issue with our latest release version?
Presumably
Can you reproduce the issue with the latest code from
main?n/a
Are you using the demo app or your own custom app?
custom
If custom app, can you reproduce the issue using our demo app?
n/a
What browser and OS are you using?
Chrome, Edge (notably not on Firefox)
What did you do?
Check our playback error metrics, and noticed unhandled errors thrown inside of Shaka. The errors are rare, in the magnitude of a handful per (tens of) thousands of plays.
Play a stream
What did you expect to happen?
Shaka plays the stream, or throws a Shaka Error.
What actually happened?
Shaka crashes with a native ReferenceError `
Have you read the FAQ and checked for duplicate open issues?
Yes
What version of Shaka Player are you using?
4.2.6
Can you reproduce the issue with our latest release version?
Presumably, need huge volumes of plays to see issue, and cannot take 4.3.X to prod.
Can you reproduce the issue with the latest code from
main?n/a
Are you using the demo app or your own custom app?
custom
If custom app, can you reproduce the issue using our demo app?
n/a
What browser and OS are you using?
Chrome, Edge (notably not on Firefox)
What did you do?
Check our playback error metrics, and noticed unhandled errors thrown inside of Shaka. The errors are rare, in the magnitude of a handful per (tens of) thousands of plays.
Play a stream
What did you expect to happen?
Shaka plays the stream, or throws a Shaka Error.
What actually happened?
Shaka crashes with a native DOMException
An attempt was made to use an object that is not, or is no longer, usableThe text was updated successfully, but these errors were encountered: