Cleaning up memory
-
Hi, I have implemented a game that adds nodes to a list; in essense it is creating a tree. When I add a node to the tree, I use malloc to create memory for the node and push it onto a stack. I then pop it from the stack and do a check. If the check passes I push it back onto the stack, if it fails, I want to delete the node so I use free() to free the memory that was created for it. What is happening when you look at the Task Manger in Windows (XP), it shows the memory being allocated and freed for the application, but when you look at the field called "Commit Charge" within Task Manager, it shows a constant rise in the amount of virtual memeory being used. This continues to grow until the program ends with a memory allocation error. My question relates to resources/links/recommendations on how to better handle memory within a C++ program. I am using Microsoft VC++, version 6.0. I've looked through the code for memory leaks, but it it appears to do as it should; allocating and releasing memory in the proper order. Since it appears that memory leaks is the cause, I am looking for links or recommendations on how to find these leaks. Any recommendations or resources would be greatly appreciated. Thanks in advance. Martin
-
Hi, I have implemented a game that adds nodes to a list; in essense it is creating a tree. When I add a node to the tree, I use malloc to create memory for the node and push it onto a stack. I then pop it from the stack and do a check. If the check passes I push it back onto the stack, if it fails, I want to delete the node so I use free() to free the memory that was created for it. What is happening when you look at the Task Manger in Windows (XP), it shows the memory being allocated and freed for the application, but when you look at the field called "Commit Charge" within Task Manager, it shows a constant rise in the amount of virtual memeory being used. This continues to grow until the program ends with a memory allocation error. My question relates to resources/links/recommendations on how to better handle memory within a C++ program. I am using Microsoft VC++, version 6.0. I've looked through the code for memory leaks, but it it appears to do as it should; allocating and releasing memory in the proper order. Since it appears that memory leaks is the cause, I am looking for links or recommendations on how to find these leaks. Any recommendations or resources would be greatly appreciated. Thanks in advance. Martin
My first question would be why are you not using the
newanddeleteoperators?
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow
-
Hi, I have implemented a game that adds nodes to a list; in essense it is creating a tree. When I add a node to the tree, I use malloc to create memory for the node and push it onto a stack. I then pop it from the stack and do a check. If the check passes I push it back onto the stack, if it fails, I want to delete the node so I use free() to free the memory that was created for it. What is happening when you look at the Task Manger in Windows (XP), it shows the memory being allocated and freed for the application, but when you look at the field called "Commit Charge" within Task Manager, it shows a constant rise in the amount of virtual memeory being used. This continues to grow until the program ends with a memory allocation error. My question relates to resources/links/recommendations on how to better handle memory within a C++ program. I am using Microsoft VC++, version 6.0. I've looked through the code for memory leaks, but it it appears to do as it should; allocating and releasing memory in the proper order. Since it appears that memory leaks is the cause, I am looking for links or recommendations on how to find these leaks. Any recommendations or resources would be greatly appreciated. Thanks in advance. Martin
Well the first thing you should do is get a memory validator program that checks for resource leaks. There are several out there, I use Bounds Checker but I sure one of the others would work just as well. It has been a while since I visited any of thier sites, but they usualy offer a 30 day free trial that you can download, so it is well worth trying. If the nodes of the tree are actualy class that allocate memory, you could be leaking it there. Since malloc and free no nothing about destructors and therefor will not call them, use new and delete instead. You could also try using the memory validation functions in the SDK, they require adding additional code to your program inorder to use them, but I understand they work quite well. I beleive there is at least one article at CP some where, on this subject. Good Luck! INTP