Here is the patch.
On Tue, Feb 13, 2018 at 3:30 PM, Gang Fan(范刚) wrote:
> Thanks for the advice, let me have another try.
>
> On Tue, Feb 13, 2018 at 4:59 AM, wm4 wrote:
>
>> On Mon, 12 Feb 2018 20:56:25 +0800
>> Gang Fan(范刚) wrote:
>>
>> > Thank
Thanks for the advice, let me have another try.
On Tue, Feb 13, 2018 at 4:59 AM, wm4 wrote:
> On Mon, 12 Feb 2018 20:56:25 +0800
> Gang Fan(范刚) wrote:
>
> > Thanks to Hendrik
> > Here is the new patch:
> >
> > From 642a413080f20f9515321e42056248e86e003997 Mon S
if (!strncmp(buf, section->fields[i].name, len)) {
--
1.9.1
On Mon, Feb 12, 2018 at 8:32 PM, Gang Fan(范刚) wrote:
> OK, should I email the new patch to the same thread or a new thread?
>
> Thanks
> Gang
>
> On Mon, Feb 12, 2018 at 7:49 PM, Hendrik
OK, should I email the new patch to the same thread or a new thread?
Thanks
Gang
On Mon, Feb 12, 2018 at 7:49 PM, Hendrik Leppkes
wrote:
> On Mon, Feb 12, 2018 at 11:55 AM, Gang Fan(范刚)
> wrote:
> > There is a potential memory leak bug in file ass_split.c, here is the
>
There is a potential memory leak bug in file ass_split.c, here is the
description.
A piece of memory is allocated on line 283. When executing the loop twice
and if the av_realloc_array returns null the function returns without
freeing the memory pointed by order.
Suggested fix:
free(order) before
