[gst-devel] memory leaks while seeking

[Benjamin Otte]

I fixed some meory leaks in the core yesterday (I made gst-typefind not
leak anymore). Dunno if some of that affected this.

(FWIW, the only error I get with stock 2.0 valgrind nowadays is "increase
... in some_header.h and recompile". After I did that everything has
worked fine ever since.)

Benjamin


On Tue, 3 Feb 2004, Jon Trowbridge wrote:

>
> Right now, there is a huge memory leak associated with seeking.  When
> viewing matrix.avi in totem, each seek increases the size of the process
> by approximately 75M.
>
> I've been trying to use valgrind to determine the source of the leaks.
> Since valgrind has trouble with threaded apps, the whole process is a
> bit touchy.  Valgrind 2.1 (the most recent devel version) works better
> than 2.0.
>
> Attached is a fragment of valgrind output describing what I think is the
> source of the leaked data.  I was hoping that someone who understood the
> core and the reference counting semantics of buffers could take a look
> and see what they thought.
>
> Thanks,
> -J
>
>