> Hi, > > A few days ago I started testing one of our POE applications with > 0.3502 and noticed a sizeable memory leak in the main process. The > application runs for several months at a time in production under > 0.3101 with never a hint of memory creep. > > After much debugging I remembered that POE::XS::Queue::Array had been > made the preferred implementation and had been installed on our > development server. Removing it clears up the leak, or at least makes > it orders of magnitude less.
Hi, I'm the author of POE::XS::Queue::Array. For now I'd consider POE::XS::Queue::Array experimental. I've had a crash problem reported on Win32, which I haven't been able to debug. I haven't been able to reproduce them on Linux either, using valgrind to attempt to track questionable memory accesses. I've had vague reports of memory leaks before, but hopefully your example code will give me something that I can use to isolate the problem. With work and other projects I haven't had the time to track down POE::XS::Queue::Array problems over the last few months, sorry if this has caused you any problems. (Sorry, I wasn't subscribed, and mutt won't let me set References <sigh>, so this won't thread properly.) Tony
