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
'.'.IO.watch; loop {1+1}; #eats all the memory #4888
Comments
From xaduha@gmail.comTested on linux with rakudo-star-2015.11, both MoarVM and JVM. On JVM it fails eventually with Method 'watch' not found for invocant of class 'IO::Path' |
From xaduha@gmail.comhttp://doc.perl6.org/type/IO​::Path#method_watch says:
My bad, JVM is off the hook. |
From @timoOn Fri Dec 18 01:19:18 2015, xaduha@gmail.com wrote:
The problem that's causing the leak is we're marking lots of things to "be freed at a safe point" (mostly frames apparently) but we never reach any safepoint, so the "to be freed" things as well as the list of things to free at the safepoint end up consuming more and more memory. |
The RT System itself - Status changed from 'new' to 'open' |
xaduha@gmail.com - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#126956 (status was 'resolved')
Searchable as RT126956$
The text was updated successfully, but these errors were encountered: