Matt, You were right, thanks man for the tips. It was an failure to shut down a session combined with a cache issue. Setting no_cache also helped a lot.
Thank you, Z On 6/19/07, Matt S Trout <[EMAIL PROTECTED]> wrote:
On Tue, Jun 19, 2007 at 04:30:39PM -0400, Zack Payton wrote: > Correction: > > Known issue misreported: > http://www.annocpan.org/~DSNOPEK/POE-Component-MessageQueue-0.1.3/lib/POE/Component/MessageQueue.pm > > You're right it is silly, but timing is off the essence, and a replacement > is more viable at this point. Perhaps you could offer some tips for > tracking down memory leaks beyond the information given here: > http://poe.perl.org/?POE_FAQ/How_do_I_fix_memory_or_resource_leaks A replacement isn't more viable since it's almost certainly your own code leaking memory. I'd recommend Devel::Leak and Devel::LeakTrace::Fast. Quick thought: if you're doing lots of random SQL statements and you've told EasyDBI to use prepare_cached then it's going to hang onto a -lot- of $sth objects and you might find that periodically forcing it to disconnect is the answer. -- Matt S Trout Need help with your Catalyst or DBIx::Class project? Technical Director Want a managed development or deployment platform? Shadowcat Systems Ltd. Contact mst (at) shadowcatsystems.co.uk for a quote http://chainsawblues.vox.com/ http://www.shadowcatsystems.co.uk/
