Re: [Valgrind-users] Basic question about memcheck

[Kaz K. <kky...@gm...>]

On Feb 24, 2010 7:36pm, Alec Matusis <ma...@ma...> wrote:
> Hi Kaz,

[...]
>
> This probably means that when I kill the program with Ctrl+C, it first
>
> releases most of the memory after the signal is caught, and only then exits,
>
> with a very small memory footprint at the very last moment, which memcheck
>
> correctly reports (corresponding to snapshot 82 in massif).

Okay, so what you have is not a leak or fragmentation, but unwanted
retention.

It might be worth looking at the logic in the Python code to see where it
might be hanging on to object references longer than necessary.