From: Nicholas N. <nj...@cs...> - 2005-05-23 19:54:31
|
On Mon, 23 May 2005, Julian Seward wrote: >> I think the problem is this: the program allocates a 4KB block, then >> frees it. Valgrind puts this block on its free list. The program then >> allocates an 8KB block. There's no block on the free list which is 8KB >> or greater, so Valgrind allocates new memory. And so on. So >> Valgrind's free list ends up holding blocks of size 4KB, 8KB, 12KB, >> 16KB, etc. Huge amounts of memory quickly get heldon the free list, >> [...] > > When you say "free list", do you mean the place where mem/addrcheck > park freed stuff for a while so as to delay its re-entry into > circulation? No. I mean the allocator's free list. N |