Re: Heap memory available (W32 console app in Visual C++)
CriCri <bitwyse@leTIRETmaquis.net> wrote:
Besides, remember that yours is not the only application running in
the system, and all of them are busy allocating and freeing memory.
Even if somehow you could get the number you are looking for, by the
time you actually try to use it, it may very well be wrong already.
Yes, but first come, first served! If I can grap a bit of heap right
NOW - too bad for the others ;-)
I'm not sure I understand this statement. Consider:
int avail = _memavl(); // 1
void* p = malloc(avail); // 2
Between 1 and 2, another process could very well have allocated some
memory, so line 2 fails. Remember - you are running under a preemptively
multitasked OS. How precisely do you plan to achieve "first come, first
served"?
It happens that I am working on a program which is very small but uses
quite a lot of memory during deeply recursive calls.
OK - if my call to malloc() fails, it's foreseen and it will exit
gracefully. So the output file is closed - empty.
But if I knew _beforehand_ that there wasn't enough memory
available, I could change the way it's handled and avoid the abnormal
termination.
Try to allocate all the memory you think you might need up front. If
this fails, you know you don't have enough.
--
With best wishes,
Igor Tandetnik
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925