Geek Answers Handbook

Debugging outofmemoryexception

In the error correction of the small ASP.NET/C# web application that I made, I encountered an OutOfMemoryException.

There are no clues as to where to look, as this is a compile-time error. How can I diagnose this exception? I guess this is exactly where memory profiling plays? Any tips?

thanks

+5
source share
4 answers

You should take a memory dump of your program at the OutOfMemoryException point in time and analyze what takes up so much memory.

Tess Ferranddes has an excellent How-To series on his blog.

+5
source

:

1) , . http://digioz.blogspot.com/2008/11/visual-studio-systemoutofmemory.html

2) VS msbuild "SolutionfileName.sln". ?

, :)

+1

, , .

, , ASP.NET.

, :

Red Gate Shaper ants

+1
source

Sorry above, but for me it happened more than three times - Redgate broke either VS or all of Windows ... Try the approach . I want the main cause of your problem to be weak debugging, check log4net . Also just if (DebuggingFlag = true) Response.Write ("DebugMsg")

can be useful as a simple and absurd sound ...

+1
source

More articles:


All Articles