Closed cristian-atehortua closed 1 year ago
I think it's fixed with https://github.com/shaka-project/shaka-player/pull/5422, can you try again against the main branch? Thanks!
Closing due to inactivity. If this is still an issue for you or if you have further questions, the OP can ask shaka-bot to reopen it by including @shaka-bot reopen
in a comment.
@shaka-bot reopen
We are still getting this error in our content with Shaka v4.3.8
v4.3.8 was released in July, and we have done 3 more releases from v4.3.x since then. The latest is v4.3.11. But there have been no changes to lib/cea/ or other relevant parts of your backtrace since v4.3.8.
Thanks for reopening.
Based on the stack trace and error code, it seems like the packet we're trying to decode ends after the first byte. If the packet is truncated for some reason, one could assume there's no useful info in it and we should ignore it (and maybe log a warning in debug mode) instead of throwing an error.
Are you willing to try a patch for us? I'm wondering if we can get away with changing this line of lib/media/closed_caption_parser.js
:
this.ceaDecoder_.extract(uint8ArrayData, captionPacket.pts);
Into this:
try {
this.ceaDecoder_.extract(uint8ArrayData, captionPacket.pts);
} catch (error) {
shaka.log.warning('CEA decoding error, ignoring packet!', error);
}
If this warning coincides with missing captions during playback, we would have to dig more deeply and figure out whether the data we need is actually in the packet or not. If it is, there would be a bug in the parser, and if not, there would be a bug in your encoder. But if this suppression of the out-of-bounds error suffices, it would be a very simple fix.
@cristian-atehortua, what do you think? Could you try it out?
Hi @joeyparrish. Thanks for your answer, I mentioned V4.3.8 because that was the one that included #5422.
I will try what you mentioned
Thanks.
@cristian-atehortua do you have any news about the test? Thanks!
Closing due to inactivity. If this is still an issue for you or if you have further questions, the OP can ask shaka-bot to reopen it by including @shaka-bot reopen
in a comment.
Have you read the FAQ and checked for duplicate open issues? Yes. It looks like is related to #3659 and #5251, however, these issues are closed now and we are still getting the same.
What version of Shaka Player are you using? 4.3.7
Can you reproduce the issue with our latest release version? Yes
Can you reproduce the issue with the latest code from
main
? Not tested, because since it happens in specific timeframes we need to put this in production.Are you using the demo app or your own custom app? Custom app.
If custom app, can you reproduce the issue using our demo app? Not yet, I will provide the results when I test since it should happen at a specific time.
What browser and OS are you using? It happens in every platform (Web in any OS, any SmartTV)
For embedded devices (smart TVs, etc.), what model and firmware version are you using? It happens in every version.
What are the manifest and license server URIs?
I will provide instructions by mail
What configuration are you using? What is the output of
player.getConfiguration()
?What did you do?
What did you expect to happen? Content should continue playback normally
What actually happened?
The 3000 - BUFFER_READ_OUT_OF_BOUNDS is thrown in some segments of this content.
Additional information Something is happening with specific segments of this content. However, on players on other platforms, this error doesn't occur. The player is able to reproduce the segment normally.
This is the stack trace of the error: