Stack memory issue with gstreamer

jbvulai jb.vu.lai at gmail.com
Fri May 2 11:17:10 PDT 2014


We did a test by changing decodebin2 to wavparse to decode our wav files. The
test is currently running but it seems to do be doing a lot better. No slow
down or crashes yet after 2 hours of playback (vs crash within 1h when
decodebin2 was used). We'd have to run the test a lot longer to be sure, as
our application is suppose to be run 24/7.

Hopefully this will be adequate workaround. Does this give you guys any hint
on what might the problem be? Maybe decodebin2's dynamic pad creation leaves
some leaks or something?



--
View this message in context: http://gstreamer-devel.966125.n4.nabble.com/Stack-memory-issue-with-gstreamer-tp4666681p4666724.html
Sent from the GStreamer-devel mailing list archive at Nabble.com.


More information about the gstreamer-devel mailing list