I have a web service that under normal conditions consume about 6-7 GB of memory. Sometimes, however, consumption spikes to 11-12 GB and I want to figure out why. For that I want to make a memory dump of the
w3wp.exe running that service so I could analyze it in a debugger offline. I make dumps with a procdump by running
procdump.exe -ma w3wp.exe
it works fine for the normal case, but when the process uses 11 GB of memory the process gets terminated by some sort of IIS protection for non-responsive app pool and
procdump terminates without creating any dump file. How do I work around that?