Memory leak in mpegtsmux

[Nicolas Dufresne]

Le mardi 20 mars 2018 à 17:09 -0700, HT a écrit :
> Under Ubuntu 14.04 with gstreamer 1.12,  specifying pids in
> mpegtsmux 
> program-map, causes memory leak, e.g. the following pipeline  leaks:
> (As 
> seen by "top")
> 
> gst-launch-1.0 videotestsrc is-live=true pattern=zone-plate kx2=20 
> ky2=20 kxy=4 kt2=10 ! video/x-raw, format=I420,width=1280,height=720
> ! 
> videoconvert ! openh264enc ! h264parse  ! muxer.sink_49 mpegtsmux 
> name=muxer prog-map=program_map,sink_49=1 ! fakesink
> 
> Whereas, this one does not:
> 
> gst-launch-1.0 videotestsrc is-live=true pattern=zone-plate kx2=20 
> ky2=20 kxy=4 kt2=10 ! video/x-raw, format=I420,width=1280,height=720
> ! 
> videoconvert ! openh264enc ! h264parse  ! mpegtsmux name=muxer  !
> fakesink
> 
>   Actually, it gets a bit more complicated. If pid is a 3 digit
> number, 
> no leaks are detected, i.e., this pipeline does not leak:
> 
> gst-launch-1.0 videotestsrc is-live=true pattern=zone-plate kx2=20 
> ky2=20 kxy=4 kt2=10 ! video/x-raw, format=I420,width=1280,height=720
> ! 
> videoconvert ! openh264enc ! h264parse ! muxer.sink_149 mpegtsmux 
> name=muxer prog-map=program_map,sink_149=1 ! fakesink
> 
> (Tried this with msdkh265 encoder, with similar results.)
> 
> Any thoughts?

Can you file a bug to bugs.gnome.org, produce GStreamer component gst-
plugins-bad. I confirm I can reproduce the run-time leak here. It get
freed when leaving, but memory is growing really fast.

thanks,
Nicolas