in reply to Re: memory (leaks and management)
in thread memory (leaks and management)
At the moment, the program is still leaking, but I haven't lost hope. I have just tried the easiest bits first. I can see the wisdom of some of the more drastic recommendations, but some pills are bitter to swallow.
Many thanks to all anyway.While I am digging, can anyone make an educated at guess at the phenomenon whereby, when I stop the program (properly, by a caught signal), and keep watching memory, said memory continues to increase (significantly) for a while, then starts decreasing until the program finally stops ? I mean, for instance does perl have to copy stuff in order to be able to destroy it ? The answer may possibly give me a clue as to what is going on.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^3: memory (leaks and management)
by soliplaya (Beadle) on Mar 29, 2007 at 23:39 UTC | |
|
Re^3: memory (leaks and management)
by perrin (Chancellor) on Mar 30, 2007 at 00:15 UTC |