[FFmpeg-devel] Question: Memory leak in muxing.c example

Stefano Sabatini stefasab at gmail.com
Fri Apr 12 00:30:07 CEST 2013

On date Thursday 2013-04-11 15:57:45 -0300, Nicolas Sugino encoded:
> Hi,
> I don't know if this is exactly where I should be posting, if it's wrong
> please tell me where.
> I tested the muxing example with valgrind and i came up a few memory leaks.
> I did this because I have been dealing with some leaks in another program
> and wanted to know how to handle more precisely the muxing.
> I executed the following line:
> valgrind --leak-check=full --leak-resolution=high --show-reachable=yes
> --log-file=test.log ./muxing test.avi
> My ffmpeg version and configure are the following:
> ffmpeg version 1.0.6 Copyright (c) 2000-2013 the FFmpeg developers
>   built on Mar 26 2013 13:36:51 with gcc 4.7.2 (GCC)
>   configuration: --prefix=/usr --disable-debug --disable-static
> --enable-avresample --enable-fontconfig --enable-gpl --enable-libass
> --enable-libbluray --enable-libfreetype --enable-libgsm --enable-libmodplug
> --enable-libmp3lame --enable-libopencore_amrnb --enable-libopencore_amrwb
> --enable-libopenjpeg --enable-libopus --enable-libpulse --enable-librtmp
> --enable-libschroedinger --enable-libspeex --enable-libtheora
> --enable-libv4l2 --enable-libvorbis --enable-libvpx --enable-libx264
> --enable-libxvid --enable-postproc --enable-runtime-cpudetect
> --enable-shared --enable-version3 --enable-x11grab

Check commit 9b211c43dc5f2e618f204c4a7fd184eb2ea51f02.

Also 1.0 is a bit old, please try and report with latest git version.
FFmpeg = Fundamentalist & Foolish Magnificient Powered Exploitable Generator

More information about the ffmpeg-devel mailing list