Re: Tracking Memory Leaks

[Bruce Waters]

There are several things that can be done. 1. Examine the log to see if the 
chunk contents are recognisable - that might tell you what part of your code 
is generating the chunks. 2. Look at the size of the chunks, and go through 
your code to see where you allocate heap storage for structs, classes, etc - 
you can write some little code snippets to run at the start of your app in 
the debugger, and use sizeof() to get feedback about how big your structs 
and classes are - then if you match the size of a leaked chunk to one of the 
sizes of your structs or classes or buffers, you have a good idea of what is 
being leaked. 3. disabling code (already mentioned) is very helpful 
too. --Bruce 


--
For information on using the PalmSource Developer Forums, or to unsubscribe, 
please see http://www.palmos.com/dev/support/forums/