[gstreamer-bugs] [Bug 554545] New: Memory leak using pulldriven pipeline

GStreamer (bugzilla.gnome.org) bugzilla-daemon at bugzilla.gnome.org
Wed Oct 1 03:14:46 PDT 2008


If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=554545

  GStreamer | gst-python | Ver: HEAD CVS
           Summary: Memory leak using pulldriven pipeline
           Product: GStreamer
           Version: HEAD CVS
          Platform: Other
        OS/Version: All
            Status: UNCONFIRMED
          Severity: critical
          Priority: Normal
         Component: gst-python
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: stefan.wehner at gmail.com
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


Please describe the problem:
It looks like when using a python element driving the pipeline in pull-mode the
call to sinkpad.pull_range(..) leaks memory (all buffers are leaked).



Steps to reproduce:
The setup is as follows:

fakesrc | puller | fakesink

The puller element is written in Python (I'll attach code).

This only happens when the puller element calls pull_range() - python sources
with a pulling fakesink work correctly and pullers that don't call pull_range()
(but instanaiate buffers themselves) work perfectly, too.

Actual results:
When executing with GST_DEBUG=5 one can that the buffers don't get unreffed
enough and don't get freed, thus leaking a lot of memory.


Expected results:


Does this happen every time?
Yes

Other information:


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=554545.




More information about the Gstreamer-bugs mailing list