Sorry, it was an old patch that I had delayed to submit for various reasons.
Glad it's fixed.
/Hubbe
On Thu, Oct 26, 2017 at 9:57 AM, James Almer <jamr...@gmail.com> wrote:
> On 10/24/2017 8:09 PM, Moritz Barsnick wrote:
> > On Tue, Oct 24, 2017 at 19:38:58 -0300, James Almer wrote:
> >>> Subject: [PATCH] Fix minor ffmpeg memory leak in id3v2 parsing.
> >>>
> >>> Reviewed-on: https://chromium-review.googlesource.com/439405
> >>> Reviewed-by: Dale Curtis <dalecur...@chromium.org>
> > [...]
> >> This doesn't seem to apply to git head, or even the recently cut 3.4
> >> branch. Was this patch made for the 3.3 branch?
> >
> > This code was changed/fixed on master 20 days ago by
> > 1fd80106be3dca9fa0ea13fb364c8d221bd27c15, even before 3.4 was branched.
> >
> > The fix may be valid for < 3.4 nonetheless. Is Chromium not using
> > master?
> >
> > Moritz
>
> They may be using master but didn't fetch new commits since late
> September or similar.
>
> Pushed to 3.3 branch in any case. It will be in the 3.3.5 release.
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
