How do I solve the "Out of Memory Exception" error in c# console Application

Question

1.00/5 (2 votes)

See more:

This console application never stop. always in running mode. Why automatic garbage collection not happening?

Please help me.
Thanks.

Posted 26-Mar-14 1:14am

Math08avan

Updated 6-Apr-14 17:39pm

v4

Add a Solution

Comments

ZurdoDev 26-Mar-14 7:18am

Maybe it is happening. Perhaps you have an infinite loop that is eating up the memory.

[no name] 26-Mar-14 7:27am

Hi, in c# automatic garbage collection predefined right. no need to write any coding.

Kornfeld Eliyahu Peter 26-Mar-14 7:33am

But you have to release your object, before GC can collect them!

ZurdoDev 26-Mar-14 7:40am

Correct. All you need to do is make sure you are disposing of your objects properly. That may mean that they go out of scope, or it may mean that you have them in a using statement, etc.

Kornfeld Eliyahu Peter 26-Mar-14 7:22am

Do you have the code? We may figure out some answers from there...

[no name] 26-Mar-14 7:29am

Hi, i have a very big code. i am not able post here. but in my code, i am using lot of data table to filter my required values.

Maarten Kools 26-Mar-14 7:36am

If you don't post code we cannot help you. We cannot look on your hard drive, see your screen or read your mind. As RyanDev suggested, it might be an infinite loop that's allocating memory. There might be many reasons the Garbage Collector doesn't run (objects might still be in use for example, again, impossible to tell without seeing code).

[no name] 26-Mar-14 7:51am

i thought, this issue may be a common issue, that's i didn't include the code. sorry for that

[no name] 26-Mar-14 7:37am

Then how would you expect us to see what you have done wrong in your code if you do not show it to us? Crystal ball? Telepathy? Tarot cards? We would have no idea what "lot of data table" even means.

[no name] 26-Mar-14 7:51am

i thought, this issue may be a common issue, that's i didn't include the code. sorry for that

Richard MacCutchan 26-Mar-14 7:54am

No one is going to struggle through that amount of code. Do some proper debugging to find out where it is looping.

OriginalGriff 26-Mar-14 8:08am

Have you ever heard of the concept of "modular coding"? No? Thought not...

In fact it would probably help you - because objects would go out of scope when you exited a method, which means that the objects would be available to the GC for collection. So give it a try: break that monolithic method into a number of smaller, simpler methods and see if the problem goes away. If it does, then ok. If it doesn't then at least it should give you a better clue as to which part of the code is giving you a problem...and make it a lot, lot more readable for us.

CHill60 26-Mar-14 9:32am

Definitely the solution to this so far!

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Fueled By Decaff · Accepted Answer · 2014-04-01T02:05:00

The garbage collector is probably still running and working, but you are not releasing any of the memory that you are using. This program reads what is presumable a rather large file into memory to process, so if this file is larger then the amount of memory available then you will need to look into another method of accessing this file.

Two debugging techniques that can help work out why this application never finishes are:

1) Put lots of System.Diagnostics.Debug.WriteLine("Specific line identifier"); messages in the code and look at the output window to see what lines are being executed when it gets stuck. Look at why the loop never terminates. Tip: in a for (;;) loop include the index as part of the debug message.

2) Comment out huge swathes of code until the application successfully runs through. When it does re-introduce the commented code until it does not finish and you have found your problem code.