Stack memory issue with gstreamer

jbvulai jb.vu.lai at gmail.com
Thu May 1 13:26:21 PDT 2014


Hi Haakon,

1. I don't have a definite value for how many bytes are leaking each
iteration, but from what i could tell the stack grows a bit less than 1kb
each iteration. This is according to the massif graphs. Each iteration has
either 3-4 file source changes. 

2. This is nice command, unfortunatly it did not yield and clues as it didnt
show any value.
be845000-be866000 rwxp 00000000 00:00 0          [stack]


We've also suspected about the start and join of threads, but did not where
to start where to check for this.  A thread spawning app would be a good
idea, but I don't undertstand why this would leak in the stack.

Regards,

J.B.




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


More information about the gstreamer-devel mailing list