[MPlayer-users] how to trace the memory leak?

[Brian J. Murrell]

On Sat, May 18, 2002 at 06:17:17PM +0200, Michal Seliga wrote:
> 
> I think that my version of mplayer (0.90pre4) eats too much memory. 

> I know it will not help you very much so I ask what should I do to report this problem 
> so you could repair it? ;-)

Well if you want to dig in yourself, check out dmalloc at dmalloc.com.
It is for just this sort of task.  Takes a bit to learn how to use it
though.

In most cases, before you can find the real memory leaks you have to
hunt down the "not-so-real" (one-time allocations that are not freed
because the programmer assumes the OS will return the memory to the
pool when the program exits) leaks and fix them so that they don't
distract you from the real leaks.

Dmalloc tells you how many times each allocation (in terms of
file:line) is called, so it might be obvious after reproduce the steps
that you did before.

b.

-- 
Brian J. Murrell
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.mplayerhq.hu/pipermail/mplayer-users/attachments/20020518/b67741f6/attachment.pgp>