appsink python memory leak?? unref call on sample?

Turmel, Frederic Frederic.Turmel at
Fri Apr 15 20:02:42 UTC 2016

Yes it is already set to false.  Same thing. I saw your post a while ago ;-)
The thing is that even with without appsink straight to fakesink I see the issue so appsink is not the issue.

-----Original Message-----
From: gstreamer-devel [mailto:gstreamer-devel-bounces at] On Behalf Of Tim Müller
Sent: Friday, April 15, 2016 12:36 PM
To: gstreamer-devel at
Subject: Re: appsink python memory leak?? unref call on sample?

On Fri, 2016-04-15 at 19:09 +0000, Turmel, Frederic wrote:


> Further test results, it looks like something is wrong with the python 
> binding:
> gst-launch-1.0 -v udpsrc uri=udp:// buffer-
> size=50000000 ! tsdemux program-number=1 ! fakesink  NO MEMORY LEAK 
> python udpsrc->tsdemux program-number=1->appsink    MEMORY LEAK python 
> udpsrc->tsdemux program-number=1->fakesink   MEMORY LEAK
> All test using the same multicast source and property. So it looks 
> like something is going with the python bindings. Any suggestion for 
> the next step?
> BTW is see the same behavior on 1.6.2 on windows
> It is possible that tsdemux emit signals that the python binding 
> cannot handle?

Out of curiosity, could you try with

  fakesink enable-last-sample=false


If you use appsink, make sure to pull out samples.


Tim Müller, Centricular Ltd -

gstreamer-devel mailing list
gstreamer-devel at

More information about the gstreamer-devel mailing list