Skip to content
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

perl6 binary sucks up all available memory #1279

Closed
p6rt opened this issue Sep 15, 2009 · 4 comments
Closed

perl6 binary sucks up all available memory #1279

p6rt opened this issue Sep 15, 2009 · 4 comments

Comments

@p6rt
Copy link

p6rt commented Sep 15, 2009

Migrated from rt.perl.org#69152 (status was 'resolved')

Searchable as RT69152$

@p6rt
Copy link
Author

p6rt commented Sep 15, 2009

From torsten.blix@googlemail.com

Rakudo git version
a9ff309e63f1df4f271847757f7f014902d26858

1) create a new test file t/bug.t with content (see also
http://paste.lisp.org/display/87090)​:

use v6;

use Test;

plan 1;

<<<<<<< .mine
say "# foo";

ok(1==1, "1==1");

# vim​: ft=perl6

2) execute "make t/bug.t" and watch the perl6 binary sucking up lots
of memory (around 10MB/sec) and not finishing the test.

Cheers,
Torsten

@p6rt
Copy link
Author

p6rt commented Mar 20, 2010

From @moritz

Torsten Blix (via RT) wrote​:

# New Ticket Created by Torsten Blix
# Please include the string​: [perl #​69152]
# in the subject line of all future correspondence about this issue.
# <URL​: http://rt.perl.org/rt3/Ticket/Display.html?id=69152 >

Rakudo git version
a9ff309e63f1df4f271847757f7f014902d26858

1) create a new test file t/bug.t with content (see also
http://paste.lisp.org/display/87090)&#8203;:

use v6;

use Test;

plan 1;

<<<<<<< .mine
say "# foo";

ok(1==1, "1==1");

# vim​: ft=perl6

2) execute "make t/bug.t" and watch the perl6 binary sucking up lots
of memory (around 10MB/sec) and not finishing the test.

The current Rakudo (of 2010.03 release) now fails very quickly​:

Confused at line 7, near "<<<<<<< .m"

The error message could be more awesome, but that's the subject for
another ticket...

@p6rt
Copy link
Author

p6rt commented Mar 20, 2010

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

@p6rt
Copy link
Author

p6rt commented Mar 20, 2010

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

@p6rt p6rt closed this as completed Mar 20, 2010
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant