[Bug 687493] Huge memory leak using Python, Gtk+, GStreamer and vp8enc

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=687493
  GStreamer | don't know | git

--- Comment #19 from Alexandre Quessy <alexandre at quessy.net> 2013-06-20 18:41:51 UTC ---
Created an attachment (id=247378)
 --> (https://bugzilla.gnome.org/attachment.cgi?id=247378)
Test case to check for a specific memory leak bug.

Here is a C program to try to reproduce this bug and debug it in valgrind. It's
the equivalent of David Klasinc's leaking one above, plus the num-buffers
property set so that the pipeline automatically stops after a few frames. The
instructions to compile it and to run Valgrind on it are in the code.

Valgrind reports millions of "possibly lost" bytes, but that might be simply
due to the fact that Glib does unusual things with pointers that could cause
them to point into the middle of an allocated block. It reports no "definitely
lost", nor "indirectly lost" bytes.

I am trying to increase the num-buffers parameter to see if there the number of
"possibly lost" bytes increase, but my computer has only 2 processors, so it's
rather long. Maybe someone could try it with a more recent computer.

Otherwise, maybe I am doing something wrong to reproduce this bug, since I
can't reproduce an obvious memory leak.

-- 
Configure bugmail: https://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.