[FFmpeg-trac] #4937(undetermined:new): memory leak in muxing.c

FFmpeg trac at avcodec.org
Fri Oct 23 12:03:22 CEST 2015

#4937: memory leak in muxing.c
             Reporter:  blinky0815   |                    Owner:
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:
              Version:  git-master   |  undetermined
             Keywords:  leak         |               Resolution:
             Blocking:               |               Blocked By:
Analyzed by developer:  0            |  Reproduced by developer:  0

Comment (by blinky0815):

 So, the good news is that Valgrind and top do not indicate a memory leak.
 Top shows constant memory usage for the muxing process.
 And as promised I ran Massif for the full 7200 seconds, which took almost
 forever to finish.
 The output is attached to this ticket.
 The attached muxing.c contains the changes described in the initial post.
 However, memory ''does disappear'' while running the muxing example.
 To further illustrate this, I ran muxing and logged top's output into a
 file and plotted the result.
 Note that this graph really reflects the memory consumption while running
 muxing. I wasn't even in the office while it was running.

 The result so far is really strange.

Ticket URL: <https://trac.ffmpeg.org/ticket/4937#comment:10>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker

More information about the FFmpeg-trac mailing list