Hi, Jeremy.
You'd do well to run Windbg with the SOS debugging extensions.
That'll give you a good idea of what's consuming what.
See :
http://weblogs.asp.net/scottgu/archi...2/17/2551.aspx http://msdn.microsoft.com/library/de...asp?frame=true http://www.microsoft.com/whdc/devtoo...g/default.mspx http://msdn.microsoft.com/library/de...ml/dbgch02.asp
Juan T. Llibre, asp.net MVP
aspnetfaq.com :
http://www.aspnetfaq.com/
asp.net faq :
http://asp.net.do/faq/
foros de asp.net, en espaņol :
http://asp.net.do/foros/
===================================
"Jeremy Chapman" <please@Idontlikespamwrote in message
news:uNYLc601GHA.4772@TK2MSFTNGP03.phx.gbl...
Quote:
Last night I noticed a bunch of our web apps were getting out of memory exceptions. I checked
task manager on the server and the w3wp.exe process had eaten up about 780 megs of memory. I did
an IIS reset and it has solved (temporarily probably) the issue. Memory usage dropped to about 50
megs or so. This morning its up to 180megs. Can I tell what apps within asp.net are using that
memory?
>
