[FFmpeg-trac] #4484(avcodec:new): libavcodec: memory leak at libavcodec/utils.c:unrefcount_frame

FFmpeg trac at avcodec.org
Tue Apr 14 23:42:51 CEST 2015


#4484: libavcodec: memory leak at libavcodec/utils.c:unrefcount_frame
-------------------------------------+-----------------------------------
             Reporter:  faham        |                    Owner:
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:  avcodec
              Version:  unspecified  |               Resolution:
             Keywords:  leak         |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-----------------------------------

Comment (by cehoyos):

 If you want to report a memory leak, valgrind output (and only valgrind
 output) is needed.
 If you don't want to report a memory leak, please explain clearly that you
 don't want to report a memory leak.
 Please understand that "memory leak" is a well defined term and massif
 (which is a useful tool) is not able to detect memory leaks.

--
Ticket URL: <https://trac.ffmpeg.org/ticket/4484#comment:6>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker


More information about the FFmpeg-trac mailing list