Current Valgrind analysis including leak check

[Mark Kretschmann]

Ahoy,

if anyone is interested, I've just been running a Valgrind memcheck
session, including high resolution leak checking. My original
intention was to find a possible memory leak with "Watch Folders For
Changes". Several users complained about growing memory usage when
this feature is enabled. E.g here in our forum:

http://amarok.kde.org/forum/index.php/topic,16825.0.html


Here's the Valgrind parameters I used:

"valgrind --log-file=$HOME/valgrind_leakcheck_amarok_17_april_2009.txt
--num-callers=50 --suppressions=/home/mark/Documents/kde.supp
--leak-check=full --leak-resolution=med amarok --nofork"


Attached you'll find the log - it does show a number of leaks, but as
always, interpreting the log is an art in itself :)

-- 
Mark Kretschmann
Amarok Developer
www.kde.org - amarok.kde.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: valgrind_leakcheck_amarok_17_april_2009.txt.bz2
Type: application/x-bzip2
Size: 33820 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/amarok-devel/attachments/20090417/040f9c30/attachment-0001.bin