appsink python memory leak?? unref call on sample?

[Tim Müller]

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

Hi,

> Further test results, it looks like something is wrong with the
> python binding:
> 
> gst-launch-1.0 -v udpsrc uri=udp://239.1.1.1.1:5724 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.

Cheers
 -Tim

-- 
Tim Müller, Centricular Ltd - http://www.centricular.com