Worker process recycles because it reached its virtual memory limit

Question

We host a rather large (self written) ASP.NET website for our customers. It consists of a web service, a web site and a image serving web site, all three in their own virtua

Answer 1

Just as an observation... If your "image serving" site happens to do any inline image processing/generation, you can quickly swallow up memory by not calling Dispose() on any disposable resources - particularly those that are wrapping native functionality...

It's not a direct answer to your question, but it might help to look into the underlying problem that is causing the rampant memory use.

Answer 2

I had the same problem with a Virtual Machine when we upgraded memory size from 4Gb to 8Gb (ironically). I found this blog which explains we can use "private memory limit" but not "virtual memory limit" with 64bit system, because : "If you are on a 64bit platform (and I am), ASP.NET app's aggressively reserve virtual memory".

http://blog.walteralmeida.com/2011/07/iis7-private-memory-limit-versus-virtual-memory-limit.html

Answer 3

This might be useful link:

http://blogs.msdn.com/tom/archive/2008/06/25/asp-net-tips-finding-what-is-taking-up-memory.aspx

(And earlier posts which explain some more context to what he's doing)

Answer 4

Try using the Windows Task Manager. On the processes tab, go to the View menu and choose Select Columns. Select the Virtual Memory Size column and then observe the value for the asp.net worker process.