Playbin leak?

[Sebastian Dröge]

On Fr, 2016-03-04 at 13:07 -0800, mrsinger wrote:
> I have a pretty simple python app.  The pipeline is built as:
>    # BUILD THE GSTREAMER PIPELINE
>     self.pipeline = Gst.Pipeline()
>     self.pipeline.set_auto_flush_bus(True)
> 
>     self.bus = self.pipeline.get_bus()
>     self.bus.set_flushing(True)
>     self.bus.add_signal_watch()
>     self.onEOS_ID = self.bus.connect('message::eos', self.OnEOS)
>     self.onError_ID = self.bus.connect('message::error',
> self.OnError)
>     
>     self.bus.enable_sync_message_emission()
>     self.onSync_ID = self.bus.connect('sync-message::element',
> self.OnSyncMessage)
> 
>     self.playbin = Gst.ElementFactory.make('playbin', None)
>     self.playbin.set_property('uri', myFile)
>     self.pipeline.add(self.playbin)
>     self.playbin.set_property('uri', "file:///myfile")
> 
>     Then setup the clock and set the state to PLAY.
> 
> 
>     At EOS, I set the state to NULL, change the uri and set the state back
> to PLAY.
> 
>     Works fine, but each new file just increases how much ram is being used.
> 
>     Anyone have an idea why?

Can you reproduce the same in a C testcase? What does massif say where
the memory is all taken?


Also you don't need to put playbin into a pipeline, playbin *is* a
pipeline :) But that should be unrelated to your problem.

-- 
Sebastian Dröge, Centricular Ltd · http://www.centricular.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 949 bytes
Desc: This is a digitally signed message part
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20160305/35dabb93/attachment-0001.sig>