[x264-devel] [PATCH] Fixed: large memory-leaks when the encoder is closed.

[Boris Nagels]

The problem occurs when I use at least two encoders, opened at the same time, from 2 separate threads.
Each thread is responsible for its own x264 encoder (opening and closing).

> On 4 Jan 2018, at 20:16, Henrik Gramner <henrik at gramner.com> wrote:
> 
> On Wed, Jan 3, 2018 at 11:22 PM, Boris Nagels <develop at focusware.nl> wrote:
>> Some more info: I didn’t use the x264 library directly, instead the calls are made from the within the ffmpeg library that I’m using (x264 encoder part).
>> Probably the leak occurs because of a combination of the 2 libraries. I’ll look in more detail at the series of calls when the memory leaks occur.
>> 
>> The leaks were reported by the “leak instrument” that is part of Xcode.
> 
> I tested valgrind with libx264 through ffmpeg CLI (latest git master
> of both ffmpeg and x264) and it does not detect any leaks or errors.
> _______________________________________________
> x264-devel mailing list
> x264-devel at videolan.org
> https://mailman.videolan.org/listinfo/x264-devel