In my first (and only) experience, the memory leaks were issues that could be eliminated. Finding them seemed to involve both intuition and carefully implemented methodology. I could locate no emulator menu option that would permit me to access variable names corresponding to memory space that had not been properly handled. In the end I had to debug the software by simply using various options built into my software to determine if, when I abruptly closed the program to return to the main Palm screen after running a specific function, the number of memory leaks was zero or some finite number.
In some screens and options, I only created one or two variables before saving to the database. If by closing abruptly after only entering that screen or using a specific function associated with it there were two memory leaks, I could logically connect them to the two variables associated with a specific data entry screen function. By this method, you can, perhaps, directly identify the buggy code. There is more in prior threads regarding this memory leak problem and how to debug it. I must admit the methods suggested were of no use to me in practical terms as they seemed to indicate the need to connect hexadecimal memory addresses to specific, variable related, memory space that had not been appropriately deallocated. Good luck. Just remember: If it's Palm OS development oriented, it's got to be easy. :-) ----- Original Message ----- From: "Eduardo Orea" <[EMAIL PROTECTED]> Newsgroups: palm-dev-forum To: "Palm Developer Forum" <[email protected]> Sent: Friday, May 26, 2006 2:44 PM Subject: Re: Memory Leak > Carlos. > > Could you try to debug this a little more, so can help you better. This > could be generated by a lot of different things, i.e. for overFreeing a > memory chunk, or an iexisten one, or you could be trying to free a MemHandle > used to store the result of DmNewRecord() after calling DmReleaseRecord(), > and so on. > > Eduardo Orea. > > "Carlos Gonzalez" <[EMAIL PROTECTED]> escribió en el mensaje > news:[EMAIL PROTECTED] > > thanks, the problem is that my debuger fails when try to launch, this > > started happening just today... I have no idea why. > > > > Also when I run my application in my palm, it gives me this error: > > MemoryMgr.C, Line 4384, Free Handle . > > > > Carlos > > > > > > -- > For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/ > -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
