Stack memory issue with gstreamer
Nicolas Dufresne
nicolas.dufresne at collabora.com
Thu May 1 09:50:49 PDT 2014
Le jeudi 01 mai 2014 à 09:28 -0700, jbvulai a écrit :
> Another note, we're using Gstreamer in a QT embedded application. We had to
> enable the support for glib in order for Gstreamer callbacks to properly
> work. I suppose qt intergrates gstreamer in its own loop... but might this
> cause problems if not handled properly?
GStreamer does require GLib main loops, but offers an integration that
is convenient. I have not idea how QT integrate the GLib mainloop, but I
doubt this is the issue.
Would it be possible to provide details on how you switch between
files ? You should also look for a growing number of threads, that might
be what is "leaking" stack memory. For this, I'd suggest using GDB, with
command "info threads", then you can get all thread backtrace using
"thread apply all bt". The backtrace will help identify what the threads
are for. Keep in mind that GStreamer 0.10 is no longer supported, so
it's up to you to analyze the results and identify fixes. Though, we
will provide you hints and tools as you ask, obviously.
cheers,
Nicolas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20140501/0edbc060/attachment.sig>
More information about the gstreamer-devel
mailing list