Keith
There are two class of memory leaks; those you cause by having
circular references where your objects don't die when you think they
should due to them holding references to each other, and those leaks
caused by RB or the OS which you have little direct control over.
To identify a leak in general I use Activity Monitor on OSX and
expect to see stable memory consumption over an extended period of
time.
For leaks caused by your own RB code, the Runtime object gives you
the most insight into your object count and memory usage. Eg If you
open one of your windows, do some stuff and close it again. You'd
probably expect the memory usage to go back to it's initial level
unless you intentionally created some persistent objects.
I have a debug dialog based on taking snapshots of the runtime object
list and memory usage and showing diffs. I could dig it out if you'd
like.
Mark Nutter as a free tool that does something similar, but I've not
tried it yet.
http://bucktailsoftware.com/developer/LeakCheckClasses.v0.1a.zip
Hope this helps,
Joe Huber
_______________________________________________
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>
