🔒 Locked

Memory cleanup

Started by Lode Jul 28, 2002 at 11:43 AM 2 replies 400+ views

Original Post

Jul 28, 2002 at 11:43 AM

Hey, I have a 256*256*256 array in a program of mine, taking a total of 64 MB of memory. That is not really the problem, but the problem is that if I close the program, sometimes it actually doesn't close at all (sometimes it does, sometimes not). I can still see it running in the task manager. It didn't do that when the array was only 64*64*64. What can I do against that or can I at least somehow destroy the array before the program is closed so it isn't annoying anymore at least if it's still open? BTW it uses SDL. [edited by - Lode on July 28, 2002 12:43:40 PM]

Mexican Farmer

Jul 28, 2002 at 10:30 PM

I don''t think it is the new array size that would be causing your program to not quit, it is more likely a fault somewhere else in your code.

a person

Jul 29, 2002 at 4:31 AM

possible the freeing of the memory is taking some time. make sure you free all the ram and write logs to see how far along it gets. if things are on the swap, windows may be trying to clear up the swap.

DerekSaw

Jul 29, 2002 at 10:48 PM

Is your program entering 'deadloops'? Check your program for any limitations on using 256x256x256. Hints: are you using unsigned char to loop 0 to 256? hmm... most likely not your problem.

... are you playing multi-threads?

[edited by - DerekSaw on July 29, 2002 11:48:24 PM]

Topic Locked

This topic has been locked by a moderator. New replies are not allowed.