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

Clear VM_CHECK lock info on fork

Browse Source 
We are resetting the actual lock so we should reset this information at
the same time. Previously this caused an assertion to fail in debug
mode.
This commit is contained in:
John Hawthorn 2025-03-25 12:05:01 -07:00
parent c576e83a24
commit 8f952a1178
Notes: git 2025-03-26 02:14:43 +00:00 
Merged: https://github.com/ruby/ruby/pull/12981
1 changed files with 5 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
thread_pthread.c
View File

@ -1549,6 +1549,11 @@ thread_sched_atfork(struct rb_thread_sched *sched)
vm->ractor.sched.running_cnt = 0;
rb_native_mutex_initialize(&vm->ractor.sched.lock);
#if VM_CHECK_MODE > 0
vm->ractor.sched.lock_owner = NULL;
vm->ractor.sched.locked = false;
#endif
// rb_native_cond_destroy(&vm->ractor.sched.cond);
rb_native_cond_initialize(&vm->ractor.sched.cond);
rb_native_cond_initialize(&vm->ractor.sched.barrier_complete_cond);