[FFmpeg-devel] Patch for libx265 memory leak

[Tom Vaughan]

Any further details you or others could provide to help the x265 dev team resolve the issue would be appreciated.

Can you share your steps to reproduce this issue? What parameters were changed? Max CTU size?

Is this documentation inadequate? https://x265.readthedocs.io/en/master/api.html#build-considerations

On 11/11/24, 10:46 PM, "ffmpeg-devel on behalf of Damiano Galassi" <ffmpeg-devel-bounces at ffmpeg.org <mailto:ffmpeg-devel-bounces at ffmpeg.org> on behalf of damiog at gmail.com <mailto:damiog at gmail.com>> wrote:


On Tue, Nov 12, 2024 at 3:38 AM Zhao Zhili <quinkblack at foxmail.com <mailto: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.
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel at ffmpeg.org <mailto:ffmpeg-devel at ffmpeg.org>
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel <https://ffmpeg.org/mailman/listinfo/ffmpeg-devel>


To unsubscribe, visit link above, or email
ffmpeg-devel-request at ffmpeg.org <mailto:ffmpeg-devel-request at ffmpeg.org> with subject "unsubscribe".