comment on

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?
A: He wanted to escape the match.

In reply to Re: Re: Detailed memory dumps (leak hunting) by Vennis
in thread Detailed memory dumps (leak hunting) by Vennis

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Think about Loose Coupling
	PerlMonks