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
WARNING: unhandled Failure detected in DESTROY #6097
Comments
From @zoffixznetThe code in Failure.pm has: # "Shouldn't happen." We use note here because the dynamic scope in GC is likely meaningless. However, it does happen with this code: Output: zoffix@VirtualBox:~$ perl6 /tmp/z.map.p6 WARNING: unhandled Failure detected in DESTROY: WARNING: unhandled Failure detected in DESTROY: WARNING: unhandled Failure detected in DESTROY: Cannot find method 'keys': no method cache and no .^find_method zoffix@VirtualBox:~$ perl6 /tmp/z.map.p6 zoffix@VirtualBox:~$ zoffix@VirtualBox:~$ perl6 -v |
From jarkko@viidakko.fiI'm also seeing this and it definitely started when I upgraded to 2017.03 Output: WARNING: unhandled Failure detected in DESTROY: Code: https://github.com/7ojo/perl6-powerline-prompt/blob/master/examples/powerline-daemon.p6 Version: perl6 -v -- |
From @zoffixznetI only now realized what this message actually means /o\ A Failure that neither exploded nor was handled got GCed, potentially indicating an error in user's code due to missed Failures. I improved the message in rakudo/rakudo@75c3f29100 |
@zoffixznet - Status changed from 'new' to 'resolved' |
Migrated from rt.perl.org#130857 (status was 'resolved')
Searchable as RT130857$
The text was updated successfully, but these errors were encountered: