On 17/10/2024 11:22, Anton Khirnov wrote:
Quoting Anton Khirnov (2023-03-15 15:45:25)
This encoder leaks and overreads, as can be seen e.g. by running an
encode under valgrind with default encoder parameters. This was known
upstream since at least 2019 (e.g. bitbucket issue #482) but never fixed
until now.
Since upstream does not seem to practice basic code hygiene, make sure
people do not use this encoder without knowing what they are getting
into.
Ping.
I still think this should be applied. The issues seem to have gotten
worse, if anything, with recent ABI breakage.
I would second this, without something drastic like this, no attention
will be brought to the quite serious issues of that encoder.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
