Debugging outofmemoryexception

Question

In the bug fixing of a small ASP.NET/C# web app I have made, I have encountered an OutOfMemoryException.

There is no tips as to where to look as this is a compile time error. How can I diagnose this exception? I am assuming this is exactly where memory profiling comes into play? Any tips?

Thanks

What exactly do you mean, it's a compile time error? Is the compiler throwing an OutOfMemoryException? — asgerhallas
– asgerhallas, Commented Apr 25, 2009 at 20:30
A compile time out of memory would indicate that you've got some REALLY weird source code. The only way that I can think of in C++ to do that would be recursive include files (i.e. a.h includes b.h while b.h includes a.h) - does C# have some similar concept? You've basically got to be doing something that's causing the parse tree to blow up. — Michael Kohne
– Michael Kohne, Commented Apr 25, 2009 at 20:40
Yes, the compiler itself is throwing the error. There is no ysod, but an error in the output window when attempting to debug. I think the culprit is I have a 3mb xml file which I parse (it has rss feeds) and then display in a custom rss feed reader. I closed the dev web server and got it sorted. — GurdeepS
– GurdeepS, Commented Apr 27, 2009 at 9:11
In my case, it was a crystal report ( RPT file) who was causing all the trouble, i exclude the file and the proyect started to work properly. — Bachask8
– Bachask8, Commented Jun 26, 2020 at 17:26

Johannes Rudolph · Accepted Answer · 2009-12-29 09:14:39Z

5

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

Tess Ferrandez has an excellent How-To series on her blog.

answered Dec 29, 2009 at 9:14

Johannes Rudolph

35.8k15 gold badges118 silver badges174 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

StevenMcD · Accepted Answer · 2009-04-25 20:35:24Z

1

There's two things I can suggest here:

1) Maybe your machine is running out of memory. Check out some ideas on http://digioz.blogspot.com/2008/11/visual-studio-systemoutofmemory.html

2) Try compiling the project outside of visual studio using the VS Command line utility and run msbuild "SolutionfileName.sln". Does your it still crash then?

Hope that helps :)

answered Apr 25, 2009 at 20:35

StevenMcD

17.6k12 gold badges46 silver badges56 bronze badges

Comments

tofi9 · Accepted Answer · 2009-04-27 03:02:40Z

1

I hope you mean runtime error, and not compile-time error.

Typically this would happen if you have a list growing, which is saved in a static field or a system-wide ASP.NET container.

You can run the application in a profiler, like:

Red gate ants profiler

answered Apr 27, 2009 at 3:02

tofi9

5,8634 gold badges32 silver badges51 bronze badges

Comments

Yordan Georgiev · Accepted Answer · 2009-04-30 11:01:02Z

1

Sorry above, but to me it has happened more than 3 times - Redgate broke either VS or the whole Windows ... Try this approach. I quess the root cause for your problem is weak debugging , check log4net. Also simple if ( DebuggingFlag == true ) Response.Write ( "DebugMsg" )

might be useful as simple and absurd it sounds ...

answered Apr 30, 2009 at 11:01

Yordan Georgiev

5,4902 gold badges60 silver badges58 bronze badges

Collectives™ on Stack Overflow

Debugging outofmemoryexception

4 Answers 4

Comments

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related