Package: mhonarc
Version: 2.6.10-1
Severity: normal
*** Please type your report below this line ***
Mbox (echo =?us-ascii?B?`echo -n "base64 subj"|base64-encode`?=)
--
.
Subject: =?us-ascii?B?YmFzZTY0IHN1Ymo=?=
.
--
RC-file
---
Package: perl
Version: 5.8.4-8
Severity: normal
*** Please type your report below this line ***
Small perl program for demonstration problem:
my $nop;
print "1st:",`grep ^VmSize /proc/$$/status`;
my $s="A" x 500;
print "2nd:",`grep ^VmSize /proc/$$/status`;
$s =~s{(.)}{$1}gxe
Package: perl-debug
Version: 5.8.4-8
Severity: normal
*** Please type your report below this line ***
Get "usemymalloc" from Config.
$debugperl -MConfig -le 'print "usemymalloc is ".$Config::Config{usemymalloc}'
usemymalloc is n
Review debian perl source:
$ grep -A6 debugperl perl-5.8.4/debian
Package: mhonarc
Version: 2.6.10-1
Severity: normal
*** Please type your report below this line ***
On my system (512Mb RAM & 1300Mb swap) mhonarc fail
with "out of memory" error. Mailbox size for processing
approximately 30Mb.
Huge memory need for "s{}{}" operator at /usr/share/mhonarc/MHonAr
On Fri, 7 Oct 2005, Jeff Breidenbach wrote:
> Is the fundamental problem in perl, mhonarc, or both?
>
fundamental problem in perl:
s{...}{...;;}g operation on 10Mb string require about 1Gb memory.
fundamental problem in mhonarc:
using perl... :-)
Perl operation don't regulate memory usage
Package: perl
Version: 5.8.4-8
Severity: normal
*** Please type your report below this line ***
Small perl program:
$a="AAA\n";
$b=$a x 100;
print "Length = ".length($b)."\n";
system("top -b -n 1 |grep \" *$$ \"");
$b=$a x 10
6 matches
Mail list logo
