Hm, looks like none of those valgrind logs catch memory leaks. I don't know valgrind too well, but I think you need to run it in "massif" mode, which is for leaks (unlike the standard mode which catches allocation/access errors).
http://developer.gnome.org/doc/guides/optimisation/Massif.html has some documentation about this.
Hm, looks like none of those valgrind logs catch memory leaks. I don't know valgrind too well, but I think you need to run it in "massif" mode, which is for leaks (unlike the standard mode which catches allocation/access errors).
http:// developer. gnome.org/ doc/guides/ optimisation/ Massif. html has some documentation about this.