[gstreamer-bugs] [Bug 581790] memory leak when changing state from ready to playing to ready

[GStreamer (bugzilla.gnome.org)]

http://bugzilla.gnome.org/show_bug.cgi?id=581790



--- Comment #4 from Jarkko Palviainen <jarkko.palviainen at sesca.com> 2009-09-02 07:20:27 UTC ---
Created an attachment (id=142300)
C version of the first test case.

I had some issues with my python, which disappeared after upgrading packages. 

Meanwhile, I rewrote the example with C. I can observe that the memory
consumption (ps aux, RSS field) raises steadily when you keep changing the
states in a loop. The additional memory is not freed when the pipeline is
destructed. I don't think there is any major leaks since you really have to
change the state hundreds or thousands times to see any significant effect, but
it still puzzles me. 

Valgrind didn't tell me clearly what could be the problem. there are some
possibly leaks/still reachable memory, but not enough to cover the memory
addition. I run it like:
$ valgrind --tool=memcheck --leak-check=full --show-reachable=yes ./test 1000

Maybe someone else can come up with better ideas with the C test case.

-- 
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.