Vitor <vitor1...@gmail.com> added the comment: Using
vi...@vitor:~$ valgrind ffmpeg_g -i /tmp/unexisting_file /tmp/out.avi ==12603== Memcheck, a memory error detector ==12603== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al. ==12603== Using Valgrind-3.6.0.SVN-Debian and LibVEX; rerun with -h for copyright info ==12603== Command: ./ffmpeg_g -i /tmp/unexisting_file /tmp/out.avi ==12603== FFmpeg version SVN-r24456, Copyright (c) 2000-2010 the FFmpeg developers built on Jul 23 2010 11:58:11 with gcc 4.4.3 configuration: --cc='ccache gcc' --cpu='host' --samples='/home/vitor/ffmpeg/fate/fate-suite' libavutil 50.23. 0 / 50.23. 0 libavcore 0. 0. 0 / 0. 0. 0 libavcodec 52.84. 0 / 52.84. 0 libavformat 52.76. 0 / 52.76. 0 libavdevice 52. 2. 0 / 52. 2. 0 libavfilter 1.26. 1 / 1.26. 1 libswscale 0.11. 0 / 0.11. 0 /tmp/unexisting_file: No such file or directory ==12603== ==12603== HEAP SUMMARY: ==12603== in use at exit: 0 bytes in 0 blocks ==12603== total heap usage: 9 allocs, 9 frees, 41,869 bytes allocated ==12603== ==12603== All heap blocks were freed -- no leaks are possible ==12603== ==12603== For counts of detected and suppressed errors, rerun with: -v ==12603== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 29 from 8) So how does ffmpeg.c not leak mem? -Vitor ________________________________________________ FFmpeg issue tracker <iss...@roundup.ffmpeg.org> <https://roundup.ffmpeg.org/issue2126> ________________________________________________
