valgrind

["Joe Van Dyk" <joevandyk gmail com>]

Hi,

How normal is it to see valgrind reporting leaked memory in a gtkmm
application running on Linux?  My trivial application shows leaked
memory before the GUI pops up, and then no errors while the GUI is
running.

That's ok, right?

Here's a recent error summary:

==21560== ERROR SUMMARY: 23 errors from 8 contexts (suppressed: 87 from 1)
==21560== malloc/free: in use at exit: 1,206,453 bytes in 12,004 blocks.
==21560== malloc/free: 98,774 allocs, 86,770 frees, 9,325,163 bytes allocated.
==21560== For counts of detected errors, rerun with: -v
==21560== searching for pointers to 12,004 not-freed blocks.
==21560== checked 1,855,548 bytes.
==21560==
==21560== LEAK SUMMARY:
==21560==    definitely lost: 220 bytes in 13 blocks.
==21560==      possibly lost: 71,040 bytes in 72 blocks.
==21560==    still reachable: 1,135,193 bytes in 11,919 blocks.
==21560==         suppressed: 0 bytes in 0 blocks.
==21560== Use --leak-check=full to see details of leaked memory.

Thanks,
Joe