[Bug 792950] New: memory leak seen during glvideomixer pipeline execution

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=792950

            Bug ID: 792950
           Summary: memory leak seen during glvideomixer pipeline
                    execution
    Classification: Platform
           Product: GStreamer
           Version: 1.12.4
                OS: Linux
            Status: NEW
          Severity: blocker
          Priority: Normal
         Component: gst-plugins-bad
          Assignee: gstreamer-bugs at lists.freedesktop.org
          Reporter: tapascst at gmail.com
        QA Contact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---

I run below command to broadcast in youtube from my 1080p rtsp camera : 

gst-launch-1.0  glvideomixer name=mix ! gldownload ! video/x-raw, width=1920,
height=1080 ! vaapih264enc dct8x8=true cabac=true rate-control=cbr bitrate=8192
keyframe-period=60 max-bframes=0 ! flvmux name=mux ! queue ! progressreport !
queue ! rtmpsink sync=true async=true
location="rtmp://x.rtmp.youtube.com/live2/xxxxxx live=1" pulsesrc
do-timestamp=true device="alsa_input.pci-0000_00_1b.0.analog-stereo" ! queue
max-size-buffers=0 max-size-bytes=0 max-size-time=0 ! audioconvert
noise-shaping=4 ! queue ! audioamplify amplification=1.0 clipping-method=1 !
queue ! voaacenc bitrate=128000 ! queue ! entransshift delay=100000
running-time=true ! queue ! mux. rtspsrc
location="rtsp://userid:password@ip:port/cam/realmonitor?channel=1&subtype=0"
latency=2000 do-retransmission=true ! queue max-size-buffers=0 max-size-bytes=0
max-size-time=0 ! rtph264depay ! entransshift delay=0 running-time=true !
identity sync=true ! h264parse ! queue ! vaapih264dec ! queue ! glupload !
queue ! glcolorbalance ! queue ! mix.

Then I run 'htop' in 2nd terminal. I can see steady buildup of memory usage by
gstreamer over a period of 30mins. It started with 1.4GB usage (cpu usage 50%)
and then it is going to 1.8GB (cpu usage 130%). 

Pipeline also starts becoming slow and cpu usage goes high gradually . 

Interesting point is: Everything is working fine in first 2 min of
broadcasting. Problem happens only after that. and broadcasting also sees lot
of pause after 2mins because of this issue.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.