Re: Large Memory

[weismat]

Do you have circular references so that the garbage collector is not cleaning up - circular references can lead to so a memory growth. This is the most likely reason.
Another potential sources are external libraries, e.g. I have seen huge leaks with WWW-Mechanize. These are not really traceabl
I would go through the code and check everything which should be collected. From my pov there is no pragma which will help you.

[way]

OK, i guess so that I must check each variable manually, Thank you so much

[almut]

There are a several modules that might help finding and getting rid of circular references, e.g. Devel::Leak, Devel::LeakTrace, Devel::Cycle, Object::Destroyer, Devel::Monitor.