On Tue Jan 12 06:35:56 2016, coke wrote:
> [...]
> > So, is this ticket closable?
>
> Yes, thanks.
Great. I'm closing the ticket as 'resolved'.
On Thu Mar 12 08:56:50 2015, barto...@gmx.de wrote:
> I've run the script mem.p6 on with a current rakudo.moar and
> rakudo.jvm and with rakudo.parrot from Rakudo Star 2015.02. On neither
> backend there is a severe memory leak (cmp. attached files moar.txt,
> jvm.txt, parrot.txt).
>
> So, is this
I've run the script mem.p6 on with a current rakudo.moar and rakudo.jvm and
with rakudo.parrot from Rakudo Star 2015.02. On neither backend there is a
severe memory leak (cmp. attached files moar.txt, jvm.txt, parrot.txt).
So, is this ticket closable?
+2437004 = 2437004 K
+0 = 2437004 K
I have a strong suspicion that this bug is related to
https://github.com/parrot/parrot/issues/795 . As demonstrated
in that issue, Parrot tends to gobble up all available memory
even in a simple case of allocating and releasing an array,
and once the process is at the edge of its memory allocati
# New Ticket Created by Moritz Lenz
# Please include the string: [perl #120638]
# in the subject line of all future correspondence about this issue.
# https://rt.perl.org/Ticket/Display.html?id=120638 >
This script by raydiak on #perl6 leaks memory on perl6-p:
#!/usr/bin/env perl6
use v6;
