Staring at the data I generated. I'm jaw dropped. Its not that windows doesn't leave just in case space. It moves the data back and forth continuously between the same couple blocks. I am not an expert on disassembly/REing of windows, but I really dont know what to do or say at how bad the windows heap algorithm is. I dont think that this problem (copying every page like clock work between the same 2 VM blocks) can be solved on P5P. I haven't tried this realloc test with a stand alone C app. I dont know if my data has anything to do with my perl being a DEBUGGING and the -Od compiler flag some how changing the behavior of the windows malloc system (google "debug heap") through the PE header. --- via perlbug: queue: perl5 status: open https://rt.perl.org:443/rt3/Ticket/Display.html?id=9319Thread Previous | Thread Next