ruby.git/gc.c, branch v3_4_9 The Ruby Programming Language merge revision(s) 61bab1889048f758396acf671c9797d6bc52504b: [Backport #21757] 2026-01-25T07:41:13+00:00 nagachika nagachika@ruby-lang.org 2026-01-25T07:41:13+00:00 28db1b5c3d3a9a5c60762622cb0c3c36c021e8e4 [PATCH] Rename to `struct rbimpl_size_overflow_tag` This struct is used for addition not only for multiplication, so remove the word `mul`, and make the member names more descriptive. 
	[PATCH] Rename to `struct rbimpl_size_overflow_tag`

	This struct is used for addition not only for multiplication, so
	remove the word `mul`, and make the member names more descriptive.
merge revision(s) 99ff0224a564b59df3ba8fbd7911dd41a7fdde34: [Backport #21757] 2026-01-25T07:40:50+00:00 nagachika nagachika@ruby-lang.org 2026-01-25T07:40:50+00:00 c409e343fb14438c2e5304f10ad4c6919e30ac2e [PATCH] Move rbimpl_size_add_overflow from gc.c to memory.h 
	[PATCH] Move rbimpl_size_add_overflow from gc.c to memory.h
Don't modify fstrings in rb_str_tmp_frozen_no_embed_acquire (#15104) 2025-11-08T03:44:56+00:00 John Hawthorn john@hawthorn.email 2025-11-08T03:44:56+00:00 9e426489f00a1b7816e8c6f299daa6116c5f505d [Bug #21671] 
[Bug #21671]
 merge revision(s) a084fef9afc7713aa4f4111f7e826c7ca1a607c7: [Backport #21099] 2025-07-14T20:55:45+00:00 Takashi Kokubun takashikkbn@gmail.com 2025-07-14T20:55:45+00:00 58d08abef567dab582ec5f7c3dcd2b8fabdaebd6 [Bug #21099] Fix GC when Ractor list not initialized When the Ractor list is not initialized and a GC is ran at boot, then it would crash because the newobj_cache of the main Ractor is not cleared. This commit changes it to use ruby_single_main_ractor when it's available and iterate over the Ractor list when we have multiple Ractors. 
	[Bug #21099] Fix GC when Ractor list not initialized

	When the Ractor list is not initialized and a GC is ran at boot, then it
	would crash because the newobj_cache of the main Ractor is not cleared.
	This commit changes it to use ruby_single_main_ractor when it's available
	and iterate over the Ractor list when we have multiple Ractors.
merge revision(s) 7df5d65eac86940619f87da7e70bc0911097ae2f: [Backport #20981] 2025-02-14T01:47:24+00:00 Takashi Kokubun takashikkbn@gmail.com 2025-02-14T01:47:24+00:00 4bafaef0a55fdc45a7b8275a82ceb0f3e3419d00 [Bug #20981] Bring back `rb_undefine_finalizer` 
	[Bug #20981] Bring back `rb_undefine_finalizer`
Disable GC during RUBY_INTERNAL_EVENT_NEWOBJ 2024-12-23T14:03:32+00:00 Peter Zhu peter@peterzhu.ca 2024-12-20T21:48:48+00:00 f4476f0d07c781c906ed1353d8e1be5a7314d6e7 We must disable GC when running RUBY_INTERNAL_EVENT_NEWOBJ hooks because the callback could call xmalloc which could potentially trigger a GC, and a lot of code is unsafe to trigger a GC right after an object has been allocated because they perform initialization for the object and assume that the GC does not trigger before then. 
We must disable GC when running RUBY_INTERNAL_EVENT_NEWOBJ hooks because
the callback could call xmalloc which could potentially trigger a GC,
and a lot of code is unsafe to trigger a GC right after an object has
been allocated because they perform initialization for the object and
assume that the GC does not trigger before then.
Allow variables in modular_gc_dir 2024-12-22T13:10:26+00:00 Nobuyoshi Nakada nobu@ruby-lang.org 2024-12-20T07:41:58+00:00 2f2530b195008209e1d9e4e9734509d5f956fa49 Such as `$(ruby_version)`, `$(arch)` and so on. 
Such as `$(ruby_version)`, `$(arch)` and so on.
Support RUBY_MODULAR_GC with LOAD_RELATIVE 2024-12-22T13:10:26+00:00 Nobuyoshi Nakada nobu@ruby-lang.org 2024-09-30T02:24:22+00:00 626037e143886bb5d15b3c5ebf1e04fc711407fa 






Don't print bug report in asan_death_callback when no VM
2024-12-20T20:04:08+00:00

Peter Zhu
peter@peterzhu.ca

2024-12-20T19:09:19+00:00

97f55466760d89a54e82608e5c7c31fba60158ca

If we don't have the VM (e.g. printing memory leaks in LSAN after shutdown)
then we will crash when we try to print the bug report. This issue was
reported in: https://github.com/ruby/ruby/pull/12309#issuecomment-2555766525





If we don't have the VM (e.g. printing memory leaks in LSAN after shutdown)
then we will crash when we try to print the bug report. This issue was
reported in: https://github.com/ruby/ruby/pull/12309#issuecomment-2555766525







Memerror is fatal if VM cannot be unlocked.
2024-12-20T07:49:30+00:00

Matt Valentine-House
matt@eightbitraptor.com

2024-12-18T22:10:04+00:00

2f6c694977dc0cdc4766a8a921e74290963c19a7

[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>





[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>