|Think about Loose Coupling|
|( #3333=superdoc: print w/replies, xml )||Need Help??|
Maybe one of them can be helpful, thank you. I've seen them before, but i'm not sure if they will be giving me the information i need.
This, because it might not be an unreclaimed object, most objects are consistant, but more of a forgotten re-initialised hash or something.
So i thought, by determing the size of the objects at different times i can localize the memory-monster.
I already wrote a global-variable-dump procedure that's useful in this case but i can't seem to determine the actual size of declared objects and used modules.
Q: Why did the Perlmonk cross the road?
In reply to Re: Re: Detailed memory dumps (leak hunting)