From gerd.r.devel@googlemail.com

The regex-dna benchmark script (
https://github.com/perl6/perl6-examples/blob/master/shootout/regex-dna.p6.pl
) eats all available memory on 32-bit systems.

The issue can be golfed to

  my $string = 'x' x 30000;
  my @​matches = $string.match(/./, :global);

Keeping around a transcoded version of the string for every match is
to blame according to analysis by jnthn and pmichaud​:

  http://irclog.perlgeek.de/perl6/2012-06-01#i_5667563

(occurs with Rakudo 2012.05-237-geef772d, but hasn't been fixed in master yet)

From @pmichaud

Now fixed in 9388218​:

  pmichaud@​kiwi​:~/p6/rakudo$ cat x
  my $str = 'x' x 30000;
  say $str.chars;

  say 'start';
  my @​matches = $str.match(/./, :global);
  say 'done';
  say +@​matches;

  pmichaud@​kiwi​:~/p6/rakudo$ ./perl6 x
  30000
  start
  done
  30000

I'm marking this ticket as 'testneeded' for now; but someone decides we
don't really need a test for this then I'm fine with closing the ticket
immediately.

Thanks,

Pm

The RT System itself - Status changed from 'new' to 'open'

From @coke

On Sun Jul 08 22​:08​:05 2012, pmichaud wrote​:

Now fixed in 9388218​:

pmichaud@​kiwi​:\~/p6/rakudo$ cat x
my $str = 'x' x 30000;
say $str\.chars;

say 'start';
my @​matches = $str\.match\(/\./, :global\);
say 'done';
say \+@​matches;

pmichaud@​kiwi​:\~/p6/rakudo$ \./perl6 x
30000
start
done
30000

I'm marking this ticket as 'testneeded' for now; but someone decides we
don't really need a test for this then I'm fine with closing the ticket
immediately.

Thanks,

Pm

I'm not sure roast is the place for testing this sort of thing. Perhaps something like perlbench once we notice a leak and write some code that exposes it?

Closing this ticket as fixed.
--
Will "Coke" Coleda

@coke - Status changed from 'open' to 'resolved'