On Feb 24, 2010 7:36pm, Alec Matusis <[email protected]> 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. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
