Robert Swain <[email protected]> added the comment: The chrome people claim it only causes a 0.5% slowdown (though I think they're talking about the AAC out of bounds read patch, maybe not the original get_bits() overrun patch) and that that isn't statistically significant in their benchmarks.
Do you have any suggestions for checking for out of bounds reads aside from just checking with fairly large granularity whether the buffer has been exhausted and erroring out if that is the case? _____________________________________________________ FFmpeg issue tracker <[email protected]> <https://roundup.ffmpeg.org/roundup/ffmpeg/issue1356> _____________________________________________________
