Le 29/09/11 01:13, Tommaso Cucinotta a écrit :
==26690== LEAK SUMMARY:
==26690== definitely lost: 12,126 bytes in 73 blocks
==26690== indirectly lost: 18,336 bytes in 571 blocks
==26690== possibly lost: 696,631 bytes in 2,590 blocks
==26690== still reachable: 898,279 bytes in 7,833 blocks
==26690== suppressed: 0 bytes in 0 blocks
==26690== Reachable blocks (those to which a pointer was found) are not
shown.
==26690== To see them, rerun with: --leak-check=full --show-reachable=yes
Do we actually have memory leaks here ?
Looking at the log, all the errors seem to be in gtk/glib. Why do we
trigger that?
To see memory use during a program's life, use the massif tool of valgrind.
JMarc
