New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
memory leak on eval #2133
Comments
From @bbkrStar 2010.08 release Run folloing code and it will start eating up memory quite fast. $ perl6 -e 'use Test; eval_lives_ok "" for 1..10000' [11:59] <moritz_> eval '' while 1; also leaks |
From @pmichaudOn Thu, Sep 02, 2010 at 03:02:43AM -0700, Pawe� Pabian wrote:
Currently each eval() execution results in compiling and We probably need to file a Parrot ticket to get Parrot to We might be able to find a way for eval() to cache the Pm |
The RT System itself - Status changed from 'new' to 'open' |
From @cokeOn Thu, Sep 2, 2010 at 10:35 AM, Patrick R. Michaud <pmichaud@pobox.com> wrote:
I wonder if this related to http://trac.parrot.org/parrot/ticket/783 -- |
From @pmichaudOn Thu, Sep 02, 2010 at 11:20:52AM -0400, Will Coleda wrote:
Indeed it is, the script in that ticket is quite similar to the Pm |
From @cokeOn Thu Sep 02 08:37:25 2010, pmichaud wrote:
This trac ticket was closed 7 months ago: "This issue is going to be fixed with GC-able packfiles, which are high up on our TODO list of -- |
From @usev6As 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' |
1 similar comment
From @usev6As 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' |
From @MasterDuke17On Thu, 23 Oct 2014 11:55:01 -0700, bartolin@gmx.de wrote:
Memory use while running this is now constant as of Rakudo version 2017.01-221-gc2349d1a6 built on MoarVM version 2017.01-72-g542baec7 implementing Perl 6.c. |
From @MasterDuke17perl6 --version `perl6 -e 'EVAL q[] while 1'` ran for 30+ min with constant RAM used, so I'm resolving this ticket. |
@MasterDuke17 - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#77644 (status was 'resolved')
Searchable as RT77644$
The text was updated successfully, but these errors were encountered: