I think that your interpreter is having problems freeing memory associated with closures. I ran into this before, and what I had to do is to patch POE so that POE::Wheel::Run accepts arguments. Check it out here:
http://rt.cpan.org/NoAuth/Bug.html?id=1783 (the patch is against version 0.22, but should not be a problem to modify the latest revision). In some cases in my POE environment (but it does not mean it has to do with POE), I had to explicitly undef lexical variables used in closures after closures were done executing. Good luck, it can take you a while to find all the leaks, but it can be done. - Dmitri. On Mon, Mar 24, 2003 at 12:56:53AM +0100, Sebastian Freund wrote: > Hi, > > I'm going to use POE::Whel::Run in a system monitoring tool. > I implemented a cron-like functionality to start up periodic measurements, > but I've encountered a serious resource leak: Along with every > creation/destruction of POE::Wheel::Run the RSS of the monitoring process > increased. This was the knock out for my monitoring daemon. :-(
