On Mon, Jul 6, 2009 at 21:44, Gisle Aas<gi...@activestate.com> wrote: > My guess would be that this then has something to do with the response > handler code that LWP attach to responses during processing. I'll > take a look.
Yeah. It was the parse_head callback that was the culprit. Fixed with <http://github.com/gisle/libwww-perl/commit/0d2ffc5f1965ac4fe7c3915ebf6d2e3063efbc50>. I'll upload an update of LWP with this fix soonish. --Gisle > On Mon, Jul 6, 2009 at 21:23, Andy Lester<a...@petdance.com> wrote: >> >> HTTP::Response has memory cycles (leaks) in it, which WWW::Mechanize >> barfs on, assuming you have Test::Memory::Cycle installed. Gisle, is >> this something you're looking into, or do I need to TODO out all those >> tests? >> >> xoxo, >> Andy >> >> -- >> Andy Lester => a...@petdance.com => www.theworkinggeek.com => AIM:petdance >> >> >> >> >> >> --~--~---------~--~----~------------~-------~--~----~ >> You received this message because you are subscribed to the Google Groups >> "WWW::Mechanize users" group. >> To post to this group, send email to www-mechanize-us...@googlegroups.com >> To unsubscribe from this group, send email to >> www-mechanize-users+unsubscr...@googlegroups.com >> For more options, visit this group at >> http://groups.google.com/group/www-mechanize-users?hl=en >> -~----------~----~----~----~------~----~------~--~--- >> >> >
