[FFmpeg-devel] Patch for libx265 memory leak
Damiano Galassi
damiog at gmail.com
Tue Nov 12 08:36:53 EET 2024
On Tue, Nov 12, 2024 at 3:38 AM Zhao Zhili <quinkblack at foxmail.com> wrote:
>
> cleanup() release library static allocations, and I don’t see lock or
> reference count
> within x265_cleanup(). So call cleanup() will break other x265 encoder
> instance,
> right?
x265 already crashes when trying to run two encodes with different settings
in
the same process, because it's storing some instance specific data in
global variables
that are overwritten when starting a new encode.
So at least with this patch it won't leaks the global data,
but the root issue needs to be fixed in x265.
More information about the ffmpeg-devel
mailing list