in reply to how can i get a comprehensive memory-dump ?
Check out this linux memory leak monitor for a little Tk app I wrote to help you. What I did in my app, which had similar problems, is watch my memory usage with the above mentioned app, and strategically sprinkle my app with
for each hash or array of objects which I had.print 'my %hash-size = ', length Dump[\%hash], "\n";
The length of the Dump gives a pretty good indicator for the size of the hash or array. So I would just start clicking away, opening and closing, etc, and watch everything. You will see where it's happening.
The hard part is NOT identifying where the memory increase occurs, but how to remedy it, without re-writting too much of your code.
The general rule to follow is make widgets once, and learn to REUSE them, don't use create-destroy for bringing in new data.
|
|---|