[FFmpeg-trac] #2802(avformat:open): memory leak in avformat_find_stream_info

FFmpeg trac at avcodec.org
Mon Jul 22 11:12:47 CEST 2013


#2802: memory leak in avformat_find_stream_info
------------------------------------+------------------------------------
             Reporter:  sporn       |                    Owner:
                 Type:  defect      |                   Status:  open
             Priority:  normal      |                Component:  avformat
              Version:  git-master  |               Resolution:
             Keywords:  leak        |               Blocked By:
             Blocking:              |  Reproduced by developer:  1
Analyzed by developer:  0           |
------------------------------------+------------------------------------
Changes (by cehoyos):

 * status:  new => open
 * reproduced:  0 => 1


Comment:

 Replying to [comment:2 sporn]:
 > It's already taken me 9 hours to track the leak down to that method call
 and figure out it was due to the nobuffer flag.

 Maybe using valgrind (or Dr.Memory) would have allowed you to save some of
 the nine hours?

 For future tickets: If you believe it is unreasonable to provide all
 needed information (in this case: valgrind output), please provide at
 least a command line that allows to reproduce the problem.
 {{{
 $ valgrind ./ffmpeg_g -fflags nobuffer -i tests/lena.pnm
 ==4039== Memcheck, a memory error detector
 ==4039== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
 ==4039== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
 ==4039== Command: ./ffmpeg_g -fflags nobuffer -i tests/lena.pnm
 ==4039==
 ffmpeg version N-54868-g9d4dece Copyright (c) 2000-2013 the FFmpeg
 developers
   built on Jul 22 2013 11:11:33 with gcc 4.7 (SUSE Linux)
   configuration: --enable-gpl --disable-indev=jack
   libavutil      52. 40.100 / 52. 40.100
   libavcodec     55. 18.102 / 55. 18.102
   libavformat    55. 12.102 / 55. 12.102
   libavdevice    55.  3.100 / 55.  3.100
   libavfilter     3. 81.102 /  3. 81.102
   libswscale      2.  4.100 /  2.  4.100
   libswresample   0. 17.103 /  0. 17.103
   libpostproc    52.  3.100 / 52.  3.100
 Input #0, image2, from 'tests/lena.pnm':
   Duration: 00:00:00.04, start: 0.000000, bitrate: N/A
     Stream #0:0: Video: ppm, rgb24, 256x256, 25 tbr, 25 tbn, 25 tbc
 At least one output file must be specified
 ==4039==
 ==4039== HEAP SUMMARY:
 ==4039==     in use at exit: 196,748 bytes in 3 blocks
 ==4039==   total heap usage: 111 allocs, 108 frees, 591,027 bytes
 allocated
 ==4039==
 ==4039== LEAK SUMMARY:
 ==4039==    definitely lost: 24 bytes in 1 blocks
 ==4039==    indirectly lost: 196,724 bytes in 2 blocks
 ==4039==      possibly lost: 0 bytes in 0 blocks
 ==4039==    still reachable: 0 bytes in 0 blocks
 ==4039==         suppressed: 0 bytes in 0 blocks
 ==4039== Rerun with --leak-check=full to see details of leaked memory
 ==4039==
 ==4039== For counts of detected and suppressed errors, rerun with: -v
 ==4039== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 2 from 2)
 }}}

-- 
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/2802#comment:3>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker


More information about the FFmpeg-trac mailing list