[Spread-users] Another way to leak (valgrind report)

Jonathan Stanton jonathan at cnds.jhu.edu
Mon Aug 30 21:32:24 EDT 2004

Hi David,
>From the internal tracing of Spread when running your memory abuse
programs I saw the total memory used increase (as you did) but I did not
see any leaks in the actual allocated structures. My theory is that the
leak is in skiplist code which does it's own memory allocation and thus is
not traced by Spread. This valgrind report also indicates the skiplist
code is the source of most of the leak. (The other two verified valgrind
leaks are known, but not serious. One is in the yacc parser which is only
called once at startup, and the other is a structure that is also only
allocated once at startup. )
I should have remembered this earlier, but awhile ago someone reported a
leak in the skiplist code and it was fixed (and committed to cvs). You can
find the discussion in the spread-users archive. That fix occured after
3.17.2 was released. You have a cvs account, so if you could check out of
cvs and check if the leak still occurs, I'm hopeful you will find it is
already fixed.
Let me know the results.



Jonathan R. Stanton         jonathan at cs.jhu.edu                                 
Dept. of Computer Science                                                       
Johns Hopkins University                                                        

More information about the Spread-users mailing list