diff options
| author | Peter Zhu <peter@peterzhu.ca> | 2025-11-13 21:45:27 -0500 |
|---|---|---|
| committer | git <svn-admin@ruby-lang.org> | 2025-11-14 03:22:49 +0000 |
| commit | 256b4722a0dc45ee8d675db0a30f37d32a40ea88 (patch) | |
| tree | d6c15265abfd055fb338bfbcbab75abbdc96e59c /doc | |
| parent | c92a44ee685fc10ce7cf4f8865d1942eb40d2780 (diff) | |
[ruby/mmtk] Lock VM in fork hooks
If we are using multiple Ractors, other Ractors may allocate objects after
rb_gc_impl_before_fork is ran because it does not lock the VM. This can cause
the GC to be in a bad state since rb_gc_impl_before_fork may have terminated
GC threads so a GC cannot run until rb_gc_impl_after_fork is ran.
https://github.com/ruby/mmtk/commit/e4bea5676d
Diffstat (limited to 'doc')
0 files changed, 0 insertions, 0 deletions