1berry/ruby
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Memerror is fatal if VM cannot be unlocked.

Browse Source 
[Bug #20942]

If we've raised a memerror while the VM is locked, and the tag we're
jumping to has been locked at a different level to the current lock (ie.
we've locked the VM again since the tag we're jumping to) then we should
consider this memerror fatal and exit, since the tag cannot unlock the
VM.

Co-Authored-By: Peter Zhu <peter@peterzhu.ca>
This commit is contained in:
Matt Valentine-House 2024-12-18 22:10:04 +00:00
parent 978df259ca
commit 2f6c694977
Notes: git 2024-12-20 07:49:48 +00:00 
Merged: https://github.com/ruby/ruby/pull/12393
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
gc.c
View File

@ -4481,7 +4481,8 @@ rb_memerror(void)
VALUE exc = GET_VM()->special_exceptions[ruby_error_nomemory];
if (!exc ||
rb_ec_raised_p(ec, RAISED_NOMEMORY)) {
rb_ec_raised_p(ec, RAISED_NOMEMORY) ||
rb_ec_vm_lock_rec(ec) != ec->tag->lock_rec) {
fprintf(stderr, "[FATAL] failed to allocate memory\n");
exit(EXIT_FAILURE);
}