[FFmpeg-devel] [PATCH] Fix memory leak while opening input JPG that doesn't exist

Carl Eugen Hoyos cehoyos
Tue Aug 10 19:54:02 CEST 2010


Reimar D?ffinger <Reimar.Doeffinger <at> gmx.de> writes:

> The image2 demuxer certainly is not the only demuxer that can fail.

It is the only one that produces a mem-leak for non-existing files, afaict.

> Even if it wasn't possible to trigger it currently it would be a bug,
> but my guess is that it is possible to craft a mov or mkv file where on open
> the index will be read but the open function will still fail later on
> during header parsing, thus causing a memleak.

I don't disagree (I admit I haven't looked), but imo, a mem-leak caused by a
crafted (or broken) file is different from one caused by a (failing) command
line containing a non-existing file.

Carl Eugen





More information about the ffmpeg-devel mailing list