Playbin leak?

[mrsinger]

Actually embedding playbin in a pipeline was the problem.

Thanks for the tip Sebastian

Now to find the guy for did it in the first place ☺


From: Sebastian Dröge-3 [via GStreamer-devel] [mailto:ml-node+s966125n4676187h57 at n4.nabble.com]
Sent: Saturday, March 05, 2016 2:18 AM
To: Singer, Matt
Subject: Re: Playbin leak?

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<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


_______________________________________________
gstreamer-devel mailing list
[hidden email]</user/SendEmail.jtp?type=node&node=4676187&i=0>
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[http://gstreamer-devel.966125.n4.nabble.com/images/icon_attachment.gif]signature.asc (968 bytes) Download Attachment<http://gstreamer-devel.966125.n4.nabble.com/attachment/4676187/0/signature.asc>

________________________________
If you reply to this email, your message will be added to the discussion below:
http://gstreamer-devel.966125.n4.nabble.com/Playbin-leak-tp4676185p4676187.html
To unsubscribe from Playbin leak?, click here<http://gstreamer-devel.966125.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4676185&code=bWF0dC5zaW5nZXJAY29ybmVsaXVzLmNvbXw0Njc2MTg1fC01MTU2OTg4NTM=>.
NAML<http://gstreamer-devel.966125.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
The information contained in this electronic message is privileged and confidential information; intended solely for the use of the intended recipient. Retransmission, dissemination or other use that any person other than the intended recipient makes of this communication is prohibited and any reliance or decisions made based upon it are solely the responsibility of such person. If you received this in error, contact the sender immediately and destroy all copies of this e-mail.




--
View this message in context: http://gstreamer-devel.966125.n4.nabble.com/Playbin-leak-tp4676185p4676211.html
Sent from the GStreamer-devel mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20160307/00085a99/attachment.html>