Re: System.OutOfMemoryException was thrown -- how to debug?

Hi Jarno

I've had this problem before on our production webservers.

I used windbg to sovle the problem. It's a great help.

I found these links very useful:
http://blogs.msdn.com/ricom/archive/2004/12/10/279612.aspx
http://blogs.msdn.com/tess/archive/2006/02/02/523553.aspx
http://dotnetdebug.blogspot.com/2005/06/blocked-finalizer-thread.html

It was the 1st time I had used windbg, but those articles along with the
windbg/sos help made things quite easy.

Btw - turns out my problem was with user scripts inside xsl files. They were
being recompiled and reloaded into memory every time the xsl file got used.
This ended up fragmenting the memory.

Oh, I found it easier to use windbg to get a process dump of the asp.net
work process and then analyze the dump offline on my desk top.

Cheers
Greg

"Jarno Leikas" <asiastakiinnostunut@xxxxxxxxxxxxxxxx> wrote in message
news:5C2D049F-803B-403C-8D33-3957941C503B@xxxxxxxxxxxxxxxx
Hello,

we're hosting a number of web services in in Windows Server 2003. Lately
we've been getting daily problems with the server where the server just
stops
responding to user requests (from a Winform client) and just giving a
System.OutofMemoryException exception (please see the end of the message).
Only restarting aspnet_wp.exe (ASP.NET is running in IIS 5 mode) helps.

Now because this happens only in the evenings, I'm pretty sure we're
looking
at either some kind of memory fragmentation problem (see
http://blogs.msdn.com/jamesche/archive/2006/01/20/515583.aspx or an actual
memory leak).

My question is, what is the best way to start debugging this issue? My
guess
is that the CLRProfiler tool could be a good starting point, as well as
looking at memory counters. Does ASP.NET produce any kind of error log
that
could shed some light on which extensions (see below) are producing the
problem?

Currently we are running WSE 2.0 SP2 for DIME attachments. (That web
service
is my primary suspect anyways since the problems started after a big
update
where, among other things, we started using the DIME attachments).

Thanks in advance for any help! Here's the exception and a stack trace
that
our client is seeing:

* There was an exception running the extensions specified in the config
file. --> Exception of type System.OutOfMemoryException was thrown.
Source : System.Web.Services
Stack trace : at
System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage
message, WebResponse response, Stream responseStream, Boolean asyncCall)
at
System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters)



.

Relevant Pages

  • Re: .NET Application requires Local Administrator Rights
    ... silent program exit" that could occur in either managed or un-managed code. ... now - and I don't have windbg, etc set up on this PC. ... I do remember that in the demo we saw how to catch the following exception, ... With a few commands you can usually find if an exception is being thrown ...
    (microsoft.public.dotnet.general)
  • RE: AccessViolationException originating from mscorjit
    ... you need to turn-on the first chance exception handling in the ... why windbg will break successfully for you. ... Microsoft Online Community Support ... where an initial response from the community or a Microsoft Support ...
    (microsoft.public.dotnet.framework)
  • Re: Interpretting the symbols (WinDbg)
    ... Maybe better to debug that either in VB or/and VC studio and not WinDbg. ... > I was testing a VB application that hosts a server control. ... > First chance exceptions are reported before any exception handling. ...
    (microsoft.public.win32.programmer.kernel)
  • Volume Shadow Copy & Blue Screens
    ... When I analyze the memory dump with windbg it seems ... This only ever happens during backups at ... parameters are the exception record and context record. ...
    (microsoft.public.windows.file_system)
  • memory problem (unknown object in generation 0)
    ... others (windbg one and framework general one). ... and i analyze them with sos extension and sosex one ... When i look into memory, in gen 0 i see strange objects. ...
    (microsoft.public.dotnet.framework.aspnet)
Loading