How to detect memory leaks ?

anmabagima · Post by **anmabagima** » Mon Dec 14, 2009 3:59 am

Hi there,

I've set up my own GU homebrew. I tried to clear all instances I've initiated. However, sometimes the PSP crashes where I guess the root cause may be memory leaks. Is there a possability to detect memory leaks ? I'm using minpsp and eclipse as development environment.

Thanks for any hints...

Regards

m0skit0 · Post by **m0skit0** » Mon Dec 14, 2009 4:03 am

Good programming prevents memory leaks.

Raphael · Post by **Raphael** » Mon Dec 14, 2009 4:10 am

Memory leaks do not cause program crashes, unless your program comes to the point where it trys to allocate more memory which then fails and your program not handling that case properly.

If you are really concerned about memory leaks, a debug memory manager will help you detect those. One can be found on my devblog, which is an C-Version of the C++ memory manager by Paul Nettle.

Other than that, we cannot help you with your problem, as we don't have enough information.

a_noob · Post by **a_noob** » Mon Dec 14, 2009 4:18 am

You can also use mmgr to look for memory leaks if you still believe that is the cause.

anmabagima · Post by **anmabagima** » Mon Dec 14, 2009 6:09 am

m0skit0 wrote:Good programming prevents memory leaks.

You are absolutely right, but as human's we do make mistakes. And you could even search hours for this one or even get some help of tools, if there are some ;)

anmabagima · Post by **anmabagima** » Mon Dec 14, 2009 6:11 am

Raphael wrote:Memory leaks do not cause program crashes, unless your program comes to the point where it trys to allocate more memory which then fails and your program not handling that case properly.

If you are really concerned about memory leaks, a debug memory manager will help you detect those. One can be found on my devblog, which is an C-Version of the C++ memory manager by Paul Nettle.

Other than that, we cannot help you with your problem, as we don't have enough information.

Hi, thanks for that. I will try that out. I'm running my apps on C++. Therefore I would try the original as well ;o)

I'm pretty sure that the reason are memory leaks or in some circumstences wrong calculated needed memory.

Thanks.

Torch · Post by **Torch** » Mon Dec 14, 2009 1:47 pm

Is there anything like a compile time garbage collection warning system?

a_noob · Post by **a_noob** » Mon Dec 14, 2009 4:45 pm

It's cool you do not have to listen to me or Raph. We both answered this question.

Torch · Post by **Torch** » Mon Dec 14, 2009 5:52 pm

Oh, cool thats exactly what mmgr is. I has no idea. Figured it was some kind of runtime debugging tool (which I normally couldn't be bothered to setup).

a_noob · Post by **a_noob** » Tue Dec 15, 2009 12:58 am

It has a few functions. But it basically can log every malloc/calloc and it can also catch memory leaks by watching the pointers handed out via these functions. I have not used it in a while, but I think you could alter some of the code,if it doesn't already have callback support, to cause a callback situation to form a sort of error handler to maybe go back and fix the problem, or reallocate the variable with more data.