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

FFmpeg trac at avcodec.org
Fri Oct 23 19:48:19 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 Cigaes):

 No idea. I have not found any evidence that it does.

 By the way, if you suspect a program leaks memory and want to test it
 without waiting forever and without trashing your system, you should run
 it with limited allowed memory. I do this with:

 With zsh, that is done with the {{{limit}}} builtin; with other shell it
 is probably within {{{ulimit}}}. The only limit I have found to work for
 that is {{{addressspace}}}. For example:

 limit addressspace 2048M
 ffmpeg -lavfi 'testsrc, split[a][b]; [b]fifo[c]; [a][c] concat' -f null -

 (this command will eat memory by queuing frames in the fifo before concat)

 You must adjust the number so that the command does not crash immediately.
 My main build of ffmpeg requires 460M to start running due to the large
 number of shared libraries.

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

More information about the FFmpeg-trac mailing list