Your message dated Sat, 14 Sep 2013 18:53:25 +0100 with message-id <[email protected]> and subject line Re: Bug#327611: perl: Memory leak in repetition operator. has caused the Debian Bug report #327611, regarding perl: Memory leak in repetition operator. 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.) -- 327611: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=327611 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: perl Version: 5.8.4-8 Severity: normal *** Please type your report below this line *** Small perl program: $a="AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA\n"; $b=$a x 1000000; print "Length = ".length($b)."\n"; system("top -b -n 1 |grep \" *$$ \""); $b=$a x 1000000; system("top -b -n 1 |grep \" *$$ \""); undef $b; system("top -b -n 1 |grep \" *$$ \""); With strange result: Length = 72000000 1995 root 10 0 138M 138M 1040 S 0.0 27.5 0:00 perl 1995 root 11 0 207M 207M 1040 S 0.0 41.1 0:00 perl 1995 root 9 0 138M 138M 1044 S 0.0 27.5 0:00 perl 1st: $b and one "leak" 2nd: $b and two "leak" 3th: only two "leak" -- System Information: Debian Release: 3.0 APT prefers testing APT policy: (150, 'testing'), (40, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.4.27-up Locale: LANG=C, LC_CTYPE=ru_RU.koi8-r (charmap=KOI8-R) Versions of packages perl depends on: ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libdb4.2 4.2.52-18 Berkeley v4.2 Database Libraries [ ii libgdbm3 1.8.3-2 GNU dbm database routines (runtime ii perl-base 5.8.4-8 The Pathologically Eclectic Rubbis ii perl-modules 5.8.4-8 Core Perl modules -- no debconf information
--- End Message ---
--- Begin Message ---On Sun, Sep 08, 2013 at 04:35:53PM +0100, Dominic Hargreaves wrote: > On Sun, Sep 11, 2005 at 10:40:13PM +0100, Andrew Suffield wrote: > > On Sun, Sep 11, 2005 at 07:52:22PM +0400, Andrew Shirrayev wrote: > > > > Memory allocated, not release and not use for lesser object. > > > > Oh, hmm, that's probably perl's own arena allocator logic getting > > confused and failing to reuse the space. Deep voodoo, I'm not touching > > that. > > > > > Object (temporary buffer?) stay in memory w/o any reference. > > > > Stack copies. Same thing. As far as I can tell, perl thinks they're > > freed, it's just failing to put the next object in a sensible place. > > > > To quote from the documentation: > > > > Perl is a profligate wastrel when it comes to memory use. > > There is a saying that to estimate memory usage of Perl, assume > > a reasonable algorithm for memory allocation, multiply that > > estimate by 10, and while you still may miss the mark, at least > > you won't be quite so astonished. This is not absolutely true, > > but may provide a good grasp of what happens. > > Given all this, I don't see the value of keeping this report open in > the BTS. So far it seems that there is no evidence of an actual leak > (in which case the subject line would at least be inaccurate) and the > other issues are mostly an inherent part of perl's design. > > Any objections to me closing this? No responses, so closing. Cheers, Dominic.
--- End Message ---
