[gstreamer-bugs] [Bug 608533] New: Suspect memory leak in real audio stream via rtsp

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=608533
  GStreamer | gst-plugins-ugly | 0.10.13

           Summary: Suspect memory leak in real audio stream via rtsp
    Classification: Desktop
           Product: GStreamer
           Version: 0.10.13
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: Normal
         Component: gst-plugins-ugly
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: negro at interim.it
         QAContact: gstreamer-bugs at lists.sourceforge.net
      GNOME target: ---
     GNOME version: ---


Created an attachment (id=152637)
 --> (https://bugzilla.gnome.org/attachment.cgi?id=152637)
Valgrind log of gst-launch uridecodebin
uri=rtsp://live.media.rai.it/broadcast/radiodue.rm ! fakesink

I noticed a constant growth in memory footprint while running a chain decoding
a .rm stream. Narrowed down the problem to the decoding part of the chain. 

The command I'm using for the test is 

gst-launch uridecodebin uri=rtsp://live.media.rai.it/broadcast/radiodue.rm !
fakesink

The memory footprint of the command grows at the rate of ~1M every 5 mins.

It seems the leak is somewhere in the real decoding of the rtsp stream. See the
attached valgrind log of a ~5 mins run of the chain. Valgrinds mark about 1.5M
of definetely lost bytes. Command used to produce the log was:

G_SLICE=always-malloc G_DEBUG=gc-friendly GLIBCPP_FORCE_NEW=1
GLIBCXX_FORCE_NEW=1 valgrind --log-file=testchain.txt --tool=memcheck
--leak-check=full --leak-resolution=low    --trace-children=yes
--num-callers=20 -v gst-launch uridecodebin
uri=rtsp://live.media.rai.it/broadcast/radiodue.rm ! fakesink

I was unable to reproduce in valgrind using just rtspsrc
location=rtsp://live.media.rai.it/broadcast/radiodue.rm ! fakesink.

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.