We are excited to announce that the IIS.NET Forums are moving to the new Microsoft Q&A experience. Learn more >

View Complete Thread
  • Re: Locking Up / Not Responding / 500 Error

    Mar 25, 2014 06:09 PM|laurin1|LINK

    Happened again today.

    There is no way to do that using the manual means as there are way too many (too much downtime) and they keep spawning and hard to track which ones I've dumped.

    I did dump a few that were "active." Most of the processes showed 0 CPU usage during this period, but 1 was always spiking at around 25% CPU usage. I dumped several of those. However, we have another problem. I opened those dumps and all have this error message in Visual Studio:

    You cannot debug a 64-bit dump of a 32-bit process , you must collect  a 32 bit dump of a 32 process

    I did, however, watch the Work Set numbers for some of these processes spike to over 700MB!