I'm having a problem in a production environment while performing a memory intensive operation, the process gets an OOM exception. In the debugger, because my local machine is not under the same memory pressure and has access to the entire address space, I can't reproduce it. I'm pretty sure it's concurrent processing when processing this large document in memory that's the problem, but I can't verify it.
Is there a utility or a way in visual studio where you can limit the memory that the debugger can access to simulate memory pressure on the system, so I can determine under what conditions the process runs out of memory? Either external to VS or internal?