As a status update: An empty EVAL combined with "while 1" still seems to
consume more and more memory (happens on Moar, Parrot and JVM):
$ perl6 -e 'EVAL q[] while 1'
On Thu Sep 02 08:37:25 2010, pmichaud wrote:
> On Thu, Sep 02, 2010 at 11:20:52AM -0400, Will Coleda wrote:
> > > Currently each eval() execution results in compiling and
> > > loading at least two additional Parrot subs into memory
> > > that represent the eval'ed code. �As far as I can tell,
> >
On Thu, Sep 02, 2010 at 11:20:52AM -0400, Will Coleda wrote:
> > Currently each eval() execution results in compiling and
> > loading at least two additional Parrot subs into memory
> > that represent the eval'ed code. As far as I can tell,
> > once loaded there's currently no way for a Parrot Sub
On Thu, Sep 2, 2010 at 10:35 AM, Patrick R. Michaud wrote:
> On Thu, Sep 02, 2010 at 03:02:43AM -0700, Paweł Pabian wrote:
>> Star 2010.08 release
>>
>> Run folloing code and it will start eating up memory quite fast.
>>
>> $ perl6 -e 'use Test; eval_lives_ok "" for 1..1'
>>
>> [11:59] eval '
On Thu, Sep 02, 2010 at 03:02:43AM -0700, Paweł Pabian wrote:
> Star 2010.08 release
>
> Run folloing code and it will start eating up memory quite fast.
>
> $ perl6 -e 'use Test; eval_lives_ok "" for 1..1'
>
> [11:59] eval '' while 1; also leaks
> [11:59] so I think it's eval() that leaks
# New Ticket Created by Paweł Pabian
# Please include the string: [perl #77644]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org/rt3/Ticket/Display.html?id=77644 >
Star 2010.08 release
Run folloing code and it will start eating up memory quite fast.