On Fri, 2007-11-30 at 10:29 +0100, Mark wrote: > Oke the first valgrind results of nm-applet. it has leaks. > > ==5832== ERROR SUMMARY: 10 errors from 2 contexts (suppressed: 123 from 2) > ==5832== malloc/free: in use at exit: 517,672 bytes in 7,809 blocks. > ==5832== malloc/free: 27,957 allocs, 20,148 frees, 7,621,756 bytes allocated. > ==5832== For counts of detected errors, rerun with: -v > ==5832== searching for pointers to 7,809 not-freed blocks. > ==5832== checked 1,407,576 bytes. > ==5832== > ==5832== LEAK SUMMARY: > ==5832== definitely lost: 2,770 bytes in 56 blocks. > ==5832== possibly lost: 92,192 bytes in 125 blocks. > ==5832== still reachable: 422,710 bytes in 7,628 blocks. > ==5832== suppressed: 0 bytes in 0 blocks. It's only leaked 2000 bytes, you'll need to do more research on the 422000 bytes which are still reachable. > But how do i do the "massif skin" and at mmaped files.. $ valgrind --tool=massif > what is in the > actual memory usage? you have: > VM Size > Private Clean > Private Dirty > Shared Clean > Shared Dirty "Actual" memory usage doesn't exist. The "Memory" column tries to represent the cost, by counting private memory and its share of the shared memory. > And how do i see which files are open? ls /proc/[pid]/fd/ http://live.gnome.org/MemoryReduction is full of useful information, tips, and identified problems. Ross -- Ross Burton mail: ross burtonini com jabber: ross burtonini com www: http://www.burtonini.com./ PGP Fingerprint: 1A21 F5B0 D8D0 CFE3 81D4 E25A 2D09 E447 D0B4 33DF
Attachment:
signature.asc
Description: This is a digitally signed message part