Re: Memory leak in aspnet_wp.exe

From: Steve Caliendo (scaliendo_at_epion.com)
Date: 12/06/04 

Date: Mon, 6 Dec 2004 11:41:01 -0500

I've received those errors, too, and here's a few things that I've learned.

Do not use excessive arrays - they chomp memory until the session expires.
If you have 10 clients, and use Dim a(1000) somewhere in your code, that's a
ton of RAM if a() is an array of controls.

Do not overburden the wp by doing long computational things such as
interpolation of a surface. Pass them on to other processes such as dll's,
etc...

Make the session timeout as short as practical. That will free RAM more
quickly.

HTH,

Steve

"RaptorsFan" <RaptorsFan@discussions.microsoft.com> wrote in message
news:7A63A7EB-CAAB-4563-80EF-9126E659416F@microsoft.com...
> aspnet_wp process accumulates memory usage up to the point when it's more
> than 60% of available RAM (2G) and none of .NET applications function.
> Sometimes user is able to login, navigate between the pages but can't
perform
> any operations that generate thing like PDF files using Crystal Reports
etc.
> Sometimes the application can't even be loaded and sign-in page stays
blank.
> There are no events that are logged in the event viewer to point to this
> problem. However we do find these errors occasionally:
>
> "aspnet_wp.exe (PID: 3900) was recycled because it was suspected to be in
a
> deadlocked state. It did not send any responses for pending requests in
the
> last 180 seconds. This timeout may be adjusted using the <processModel
> responseDeadlockInterval> setting in machine.config. "
>
> and
>
> "aspnet_wp.exe (PID: 3328) was recycled because it failed to respond to
> ping message. "
>
> and
>
> "Failed to execute request because QueryInterface for ASP.NET runtime
> failed. Error: 0x80004005 Unspecified error "
>
> Can you tell me how we can trap or log this information so that we can
find
> what is causing the leak and solve it.
>
>

Loading