Out-Of-Memory

Gurra_Koo

I don't know. It's windows that allocate the memory so i don't have a clue...

David Crow

If you have Windows 2000 or XP, look at the Performance tab of Task Manager to see the machine's memory usage. What does it look like before and during the program's execution?

"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)

Antony M Kancidrowski

What I meant was are you allocation memory to data statically or dynamically. i.e.

char data[1000000]; // Or some large numbers

or

char* pdata;

pdata = new char[1000000];
delete [] pdata;

If you are running through the debugger you should be able to see what it is that is failing to allocate. If you look at the call stack, what is being called? Ant.

Gurra_Koo

Every thing but full...

David Crow

Which makes no sense. Look at the Task Manager before your program runs, write down the memory-related numbers. Look at the Task Manager while your program runs, write down the memory-related numbers. Compare those numbers. What do they tell you?

"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)

Gurra_Koo

That i've got plenty of memory left...

David Crow

Ok, can you post the exact verbiage of the out-of-memory message?

"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)

Gurra_Koo

It comes in a messagebox: Unhandled exception at 0x77e73887 in net32.exe: Microsoft C++ exception: CMemoryException @ 0x00f5f3a4.

Gurra_Koo

It's a malloc call. Trying to allocate 22 bytes..

David Crow

Sounds like you need to compile in debug mode, and use F5 to start the program.

"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)

David Crow

If this is a C++ program use new/delete instead.

"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)

Antony M Kancidrowski

When you look at the call stack is it calling the same function over and over again? I.e. trying to allocate 22bytes over and over again? Ant.

antlers

You may have corrupted the heap. Usually this is because you've written to an uninitialized pointer, or written before/beyong the end of an array or object that you've previously allocated on the heap.