Not enough storage is available to process this command

Question

0.00/5 (No votes)

See more:

I am calling a function recursively and which is allocating 2048 byte is being allocated in each call.At start the application is running as per requirement but later it is getting crashed by giving the error that "Not enough storage is available to process this command". And the memory allocator returns bad pointer of memory,for which the application is being crashed.can any one please help me on this issue.

Posted 16-Apr-12 23:34pm

subrata kumar Nayak

Add a Solution

Comments

Keith Barrow 17-Apr-12 5:50am

Please add some code. Obviously you are recursing so often that the memory is used up. Whether this should happen, and what can be done about it largely depends on what you are doing.

Roliking 17-Apr-12 5:54am

please add your code..

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)

OriginalGriff · Answer 1 · 2012-04-16T23:59:00

There are a couple of possibilities, the major ones are
1) Your recursive routine is being called too deep.
2) Your routine is not releasing memory when it is finished with it.
3) Your routine is allocating more memory than you think.
4) Your heap size is set too small.

The first three you may be able to fix by looking at your code. The last one you may be able to fix by increasing the size of the heap - but how you can do that (if you can) depends on the compilation system you use.

Have you checked how many calls there are to this routine?