forgot to say, the reason why the Heap* test didn't move the block until half a meg is the "process heap" isn't used by clib malloc (it creates its own heap/memory pool) so the process heap probably (I guess, I can "walk" using the Heap* API it if I had the time and check if its truly empty or not) didn't have a single alloc in it. I can't explain why perl malloc did so many moves under 250 bytes and clib malloc didn't. I might take the c debugger through perl's malloc and see if I can spot anything that might be causing it if I have the time. --- via perlbug: queue: perl5 status: open https://rt.perl.org:443/rt3/Ticket/Display.html?id=9319Thread Previous | Thread Next