aspnet_wp.exe

  • Thread starter Thread starter Vai2000
  • Start date Start date
V

Vai2000

Hi All, I am just baffled up with the Memory Usage of the ASP.NET worker
Process..
On the servers its almost 500MB..... also I am unable to kill this
process.... :(

How do I resolve this? I am doing output cache on one of the pages....

TIA
 
Memory is handled differently in .NET than it is in the COM world. The GC
fires off when needed, which is dictated by running out of memory. You can
throttle this, somewhat, through configuration, but it is not normally a
wise decision. You can also force GC on a regular basis, but you are more
likely to mess this up than add improvement.

The inability to kill the aspnet_wp is more problematic. Are you properly
closing and disposing of objects, like data connections? If not, this could
be a serious problem.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

************************************************
Think Outside the Box!
************************************************
 
Thanks, will GC.Collect help? If I incorporate that call in Page.Unload
Method? I am sure the GC is not picking up orphan resources quick enough...
I am sure that I am releasing most of the resources...esp. File IO stuff....
but some calls to other classes might not have proper destruction
process...also its beyond my reach.

Please advice.
 
It could, but be aware that taking control of the process may help memory
usage, but cause additional problems. By default, the GC fires when there is
a lack of memory. While this produces bad numbers, in task manager, it is
not really all that bad to have the memory filled versus empty, as it is
idle. If you start other processes, the query for memory will fire off the
GC in .NET.

The best advice is not to take control of the GC, unless you see other
symptoms of a problem. Task Manager memory usage is not enough to get
concerned (for reasons stated above). If an object has a Dispose() method,
call it when you get rid of it. That will guarantee the GC picks it up on
its next run.

The biggest danger is not consumption of memory, but memory not being freed
by GC when it is no longer in use. This happens when you still have an
object that appears to be in use, which most oft happens when you fail to
Dispose().

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

************************************************
Think Outside the Box!
************************************************
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Debugging aspnet_wp.exe 1
How do I attach to process in Windows Vista 4
Session.Abandon() 1
Worker process and Cache object's lifetime 1
Memory Leak in ASP.NET 2.0 Web Page 3
IIS 6 question 2
aspnet_wp.exe takes 100 % of the resources 2
aspnet_wp.exe caching and locking process 1

Back
Top