[FFmpeg-user] Suspect memory leak in NUT muxer

[Massimo Battistel]

I was joking when speaking about streaming, but not completely.

My real need is sending both audio and video through pipes (and this is not
very different from streaming in the end...). At present nut is the only
container that allows me to pass audio with no problems. If you have any
suggestion about a good container...

My final goal is sending ffmpeg output to decklink like that:

ffmpeg -i .... -f nut(or somewhat) - | bmdplay ...

thanks



2013/10/18 Paul B Mahol <onemda at gmail.com>

> On 10/18/13, Massimo Battistel <battistel at gmail.com> wrote:
> > 2013/10/18 Paul B Mahol <onemda at gmail.com>
> >
> >> On 10/18/13, Massimo Battistel <battistel at gmail.com> wrote:
> >> > hello,
> >> > with the following command line:
> >> >
> >> > ffmpeg -i any.mpg -vcodec rawvideo -acodec pcm_s16le -f nut - 2> NUL |
> >> > ffplay -
> >> >
> >> > for any video file, you can experience a substantial memory leak. Same
> >> > problem using directshow capture source (decklink). In about 12 hours
> >> > ffmpeg passed from 40mb to 550mb and ffplay from 25mb to 380mb.
> >> >
> >> > I suspect the problem is the nut muxer.
> >> > Using ASF (-f asf) as muxer everything is fine and no mem leak is
> >> detected.
> >> > I have not tested other muxers.
> >> >
> >> > ffmpeg/ffplay version used for these tests:
> >> > "N-55020-g768e40b" 64bit on Windows 7 64bit.
> >> > "N-54960-gf3f4e13" 32bit on Windows XP 32 bit.
> >> >
> >> > thanks,
> >> > MB
> >> > _______________________________________________
> >> > ffmpeg-user mailing list
> >> > ffmpeg-user at ffmpeg.org
> >> > http://ffmpeg.org/mailman/listinfo/ffmpeg-user
> >> >
> >>
> >> nut allocates memory for sync points, so more frames more memory is
> >> needed.
> >> _______________________________________________
> >> ffmpeg-user mailing list
> >> ffmpeg-user at ffmpeg.org
> >> http://ffmpeg.org/mailman/listinfo/ffmpeg-user
> >>
> >
> >
> > Do you mean that there is no mem leak and what i've experienced is the
> > normal behaviour?
> > Ok, not a good container for 24/7 streaming :-)
>
> I guess those stuff that allocates memory could be disabled
> as index seek table is not very useful in streaming, and
> index table iirc is optional.
>
> So it should be relatively trivial to add such option to muxer,
> it just nobody come with idea of using nut for 24/7 streaming until now.
> (Better ever then never)
>
> >
> > So what is the advantage of using nut over other containers?
> >
> > thanks
> > _______________________________________________
> > ffmpeg-user mailing list
> > ffmpeg-user at ffmpeg.org
> > http://ffmpeg.org/mailman/listinfo/ffmpeg-user
> >
> _______________________________________________
> ffmpeg-user mailing list
> ffmpeg-user at ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user
>



-- 
Massimo Battistel.