Is there a method to examine the virtual address space of a specific process to examine if that process is under going virtual memory fragmentation? I know it sounds like something I shouldn't be worried about, but we have a process that fails with an OutOfMemory error, but there is plenty of available memory on the system.
The process has about 500 megabytes available to it and the requested memory call was for 417 megabytes. This leads me to think there isn't enough contiguous space available. But of course I can't offer that as a problem until I can prove it.
In the past I've used Address Space Monitor (http://www.hashpling.org/asm/) and ProcMon to help me figure these types of problems out, but they're not supported on Windows 2000. Anyone have any ideas for Windows 2000?
Besides the obvious, upgrading the OS. (Trust me, that's a whole different fight) Thanks.