Hi Everyone, I know there's been some discussion lately about using POSE 3.4 to detect memory leaks. Can anyone provide more detailed (step-by-step) instructions on how to decipher these log files to hunt down the code that's causing the memory leak?
I currently have 2 memory leaks that I can't seem to get rid of. I've made sure that I'm unlocking all locked handles and that I 'DmRelease' all resources, but I still have a memory leak. I should also mention that I AM calling FrmCloseAllForms() in 'AppStop'. POSE detects the memory leaks, dumps a log file, but trying to make sense of this information is not explained anywhere in the POSE documentation. I guess what I really need is an elementary, step-by-step explanation of how to use the log file information to pin-point the code causing the memory leak. Thanks! Robert Purcell, [EMAIL PROTECTED] BapSoft, http://www.bapsoft.com __________________________________________________ Do You Yahoo!? Yahoo! Sports - Coverage of the 2002 Olympic Games http://sports.yahoo.com -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
