Your message dated Wed, 06 Jan 2010 19:21:03 +0200
with message-id <[email protected]>
and subject line closing #178564
has caused the Debian Bug report #178564,
regarding new perl 5.8 in unstable seems to have memory leak in long running
processes
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
178564: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=178564
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: perl
Version: 5.8.0-15
I did an update a few days ago to the latest unstable perl (was previously
5.6.something, also from unstable).
I have some longrunning usenet processing scripts, and it seems that the new
version of perl (I don't know if it's just the debian version, or possibly
also the upstream one) has a pretty severe memory leak.
It takes only a couple hours for one of these processes to grow to exhaust
the virtual memory of the machine (1gig ram + 1gig swap), and force the
kernel to start killing things. The exact same script worked fine
indefinitely with no significant growth past the standard 30-or-so Meg when
running under 5.6.
Let me know what additional info would help in tracking this down.
Evan
--- End Message ---
--- Begin Message ---
No test case available, so no way to reproduce. I'm closing this bug until
someone manage to provide the test case.
--
Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com
C++/Perl developer, Debian Developer
signature.asc
Description: OpenPGP digital signature
--- End Message ---
