Your message dated Fri, 30 Oct 2009 10:42:02 +0200
with message-id <[email protected]>
and subject line Re: state of #200540
has caused the Debian Bug report #200540,
regarding Possible memory leak in File::Copy move()
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.)
--
200540: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=200540
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: perl-modules
Version: 5.8.0-18
After upgrading my system from perl 5.6.1 to 5.8 in unstable (along with all
the other current libraries and dependencies), I started noticing what seems
to be an unbounded memory leak in a custom long-running perl process that
manages files.
I think I've narrowed it down to File::Copy move(), when the file is fairly
large (tens of megabytes), and when the move is across filesystem boundaries
(not a simple rename).
I replaced the call to move() with a system call to mv, and the perl script
is no longer dying with out-of-memory errors. Unfortunately, that is not a
cross-platform solution.
The strange thing is I can't seem to replicate it in a non-complex script.
If I do a simple test script that just moves files across filesystem
boundaries, it doesn't seem to exhibit the problem. So I'm not positive
that File::Copy is the real culprit. There may be some other interaction
that also has to be present, but since removing move() stopped the memory
leak in its tracks, I figured it would be good to report anyway.
If there is any additional information I can provide, please let me know.
Evan
--- End Message ---
--- Begin Message ---
Evan Harris wrote:
>
> I'm no longer running the app that exhibited the problem. Since I never
> got a response to the bug report, I never did further testing, just
> continued with the workaround of using mv.
>
I'm closing the bug then. Re-open if/when you want to trace it down.
--
Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com
C++/Perl developer, Debian Developer
signature.asc
Description: OpenPGP digital signature
--- End Message ---
