On Mar 19, 2006, at 11:56 AM, Keith Hutchison wrote:
Any pointers on how to track down memory leaks?
Avoid pointers :)
Seriously you can use DebugDumpObjects in lots of places to help track
them down.
You can put a DebugDumpObjects around calls to functions and see if
there are leaks in the functions themselves.
If you have objects referencing other objects you may want/need to have
some code that checks for cycles.
If you have two object referencing each other but nothing else in your
program can reference them then you can have a leak. That one is harder
to track down, but a "debugdumpobjects" can help locate them.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
