[x264-devel] [PATCH] Fixed: large memory-leaks when the encoder is closed.
BugMaster
BugMaster at narod.ru
Fri Jan 5 10:49:50 CET 2018
On Fri, 5 Jan 2018 10:08:52 +0100, Boris Nagels wrote:
> 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).
Hi.
Are you using the latest version of source code (i.e. b00bcafe53a166b63a179a2f41470cd13b59f927)?
Are you sure that your leak is in x264_encoder_close and not due failed x264_encoder_open
which can leak during fail.
Also you can try with attached patch but it fix not leak but
theoretical but not possible situation when h->cost_mv_fpel[i][0] was
allocated but one of h->cost_mv_fpel[i][1..3] allocation failed. This
situation is impossible because in this case we wouldn't call
x264_analyse_free_costs (at least currently).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fix.diff
Type: application/octet-stream
Size: 544 bytes
Desc: not available
URL: <http://mailman.videolan.org/pipermail/x264-devel/attachments/20180105/d747bd86/attachment.obj>
More information about the x264-devel
mailing list