June 2026 - ruby-core - ml.ruby-lang.org

[ruby-core:125704] [Ruby Bug#22104] Segfault in PRISM compiler while Bootsnap compiles aws-sdk client_api.rb
by Morred (Laura Eck) 27 Jul '26

27 Jul '26

Issue #22104 has been reported by Morred (Laura Eck). ---------------------------------------- Bug #22104: Segfault in PRISM compiler while Bootsnap compiles aws-sdk client_api.rb https://bugs.ruby-lang.org/issues/22104 * Author: Morred (Laura Eck) * Status: Open * ruby -v: 4.0.4 * Backport: 3.3: UNKNOWN, 3.4: UNKNOWN, 4.0: UNKNOWN ---------------------------------------- I'm seeing intermittent segmentation faults on aarch64-linux when Ruby compiles large auto-generated AWS SDK files, triggered through Bootsnap's ISeq compile cache. Observed while compiling: aws-sdk-dynamodb-*/lib/aws-sdk-dynamodb/client_api.rb aws-sdk-rds-*/lib/aws-sdk-rds/client_api.rb **Environment:** ruby 4.0.4 (2026-05-12 revision b89eb1bcbf) +YJIT +PRISM [aarch64-linux] I'm attaching two full backtraces including C level backtrace information: **Backtrace 1:** ``` /usr/local/bundle/ruby/4.0.0/gems/aws-sdk-dynamodb-1.165.0/lib/aws-sdk-dynamodb/client_api.rb: [BUG] Segmentation fault at 0x0000aaab1cc9e000 ruby 4.0.4 (2026-05-12 revision b89eb1bcbf) +YJIT +PRISM [aarch64-linux] -- Control frame information ----------------------------------------------- c:0073 p:---- s:0441 e:000440 l:y b:---- DUMMY [FINISH] c:0072 p:---- s:0438 e:000437 l:y b:---- CFUNC :compile_file c:0071 p:0009 s:0432 e:000431 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/bootsnap-1.24.4/lib/bootsnap/compile_cache/iseq.rb:77 [FINISH] c:0070 p:---- s:0426 e:000425 l:y b:---- CFUNC :fetch c:0069 p:0106 s:0417 e:000416 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/bootsnap-1.24.4/lib/bootsnap/compile_cache/iseq.rb:135 c:0068 p:0008 s:0409 e:000408 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/bootsnap-1.24.4/lib/bootsnap/compile_cache/iseq.rb:166 [FINISH] c:0067 p:---- s:0403 e:000402 l:y b:---- CFUNC :require c:0066 p:0033 s:0398 e:000397 l:n b:---- BLOCK /usr/local/lib/ruby/4.0.0/bundled_gems.rb:60 c:0065 p:0145 s:0392 e:000391 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/bootsnap-1.24.4/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:33 c:0064 p:0057 s:0383 e:000382 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/core_ext/kernel.rb:34 [FINISH] c:0063 p:0014 s:0375 e:000373 l:y b:0001 CLASS /usr/local/bundle/ruby/4.0.0/gems/aws-sdk-dynamodb-1.165.0/lib/aws-sdk-dynamodb/client.rb:61 c:0062 p:0008 s:0371 e:000370 l:y b:0001 CLASS /usr/local/bundle/ruby/4.0.0/gems/aws-sdk-dynamodb-1.165.0/lib/aws-sdk-dynamodb/client.rb:55 c:0061 p:0193 s:0368 e:000367 l:y b:0001 TOP /usr/local/bundle/ruby/4.0.0/gems/aws-sdk-dynamodb-1.165.0/lib/aws-sdk-dynamodb/client.rb:42 [FINISH] c:0060 p:---- s:0365 e:000364 l:y b:---- CFUNC :require c:0059 p:0033 s:0360 e:000359 l:n b:---- BLOCK /usr/local/lib/ruby/4.0.0/bundled_gems.rb:60 c:0058 p:0145 s:0354 e:000353 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/bootsnap-1.24.4/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:33 c:0057 p:0057 s:0345 e:000344 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/core_ext/kernel.rb:34 [FINISH] c:0056 p:0007 s:0337 e:000336 l:y b:0001 CLASS /usr/local/bundle/ruby/4.0.0/gems/aws-sdk-dynamodb-1.165.0/lib/aws-sdk-dynamodb/customizations/client.rb:5 c:0055 p:0007 s:0334 e:000333 l:y b:0001 CLASS /usr/local/bundle/ruby/4.0.0/gems/aws-sdk-dynamodb-1.165.0/lib/aws-sdk-dynamodb/customizations/client.rb:4 c:0054 p:0007 s:0331 e:000330 l:y b:0001 TOP /usr/local/bundle/ruby/4.0.0/gems/aws-sdk-dynamodb-1.165.0/lib/aws-sdk-dynamodb/customizations/client.rb:3 [FINISH] c:0053 p:---- s:0328 e:000327 l:y b:---- CFUNC :require c:0052 p:0033 s:0323 e:000322 l:n b:---- BLOCK /usr/local/lib/ruby/4.0.0/bundled_gems.rb:60 c:0051 p:0145 s:0317 e:000316 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/bootsnap-1.24.4/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:33 c:0050 p:0057 s:0308 e:000307 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/core_ext/kernel.rb:34 c:0049 p:0011 s:0300 e:000299 l:y b:0001 TOP /usr/local/bundle/ruby/4.0.0/gems/aws-sdk-dynamodb-1.165.0/lib/aws-sdk-dynamodb/customizations.rb:4 [FINISH] c:0048 p:---- s:0297 e:000296 l:y b:---- CFUNC :require_relative c:0047 p:0032 s:0292 e:000291 l:y b:0001 TOP /usr/local/bundle/ruby/4.0.0/gems/aws-sdk-dynamodb-1.165.0/lib/aws-sdk-dynamodb.rb:63 [FINISH] c:0046 p:---- s:0289 e:000288 l:y b:---- CFUNC :require c:0045 p:0033 s:0284 e:000283 l:n b:---- BLOCK /usr/local/lib/ruby/4.0.0/bundled_gems.rb:60 c:0044 p:0145 s:0278 e:000277 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/bootsnap-1.24.4/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:33 c:0043 p:0057 s:0269 e:000268 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/core_ext/kernel.rb:34 c:0042 p:0005 s:0261 e:000260 l:y b:0001 TOP /jeancaisse/packs/utils/app/lib/aws/dynamo_d_b.rb:3 [FINISH] c:0041 p:---- s:0258 e:000257 l:y b:---- CFUNC :require c:0040 p:0033 s:0253 e:000252 l:n b:---- BLOCK /usr/local/lib/ruby/4.0.0/bundled_gems.rb:60 c:0039 p:0145 s:0247 e:000246 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/bootsnap-1.24.4/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:33 c:0038 p:0026 s:0238 e:000237 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/core_ext/kernel.rb:26 [FINISH] c:0037 p:---- s:0230 e:000229 l:y b:---- CFUNC :const_get c:0036 p:0010 s:0224 e:000223 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/cref.rb:62 c:0035 p:0039 s:0220 e:000219 l:n b:---- BLOCK /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/loader/eager_load.rb:175 c:0034 p:0063 s:0212 e:000211 l:n b:---- BLOCK /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/loader/file_system.rb:51 [FINISH] c:0033 p:0027 s:0206 e:000205 l:y b:0001 METHOD <internal:array>:228 c:0032 p:0020 s:0200 e:000199 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/loader/file_system.rb:40 c:0031 p:0048 s:0191 e:000190 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/loader/eager_load.rb:170 c:0030 p:0010 s:0180 e:000179 l:n b:---- BLOCK /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/loader/eager_load.rb:18 [FINISH] c:0029 p:---- s:0175 e:000174 l:y b:---- CFUNC :each c:0028 p:0032 s:0171 e:000170 l:n b:---- BLOCK /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/loader/eager_load.rb:17 [FINISH] c:0027 p:0018 s:0168 e:000167 l:y b:0001 METHOD <internal:thread_sync>:130 c:0026 p:0006 s:0164 e:000163 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/loader/eager_load.rb:11 c:0025 p:0005 s:0158 e:000157 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/railties-8.1.3/lib/rails/autoloaders.rb:32 c:0024 p:0009 s:0154 e:000153 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/railties-8.1.3/lib/rails/application.rb:556 c:0023 p:0085 s:0150 e:000149 l:y b:0001 METHOD /jeancaisse/spec/account_copy_e2e_tests.rb:91 c:0022 p:0019 s:0137 e:000136 l:n b:---- BLOCK /jeancaisse/spec/account_copy_e2e_tests.rb:128 c:0021 p:0006 s:0134 e:000133 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/rspec-mocks-3.13.8/lib/rspec/mocks.rb:96 c:0020 p:0043 s:0129 E:002088 l:y b:0001 TOP /jeancaisse/spec/account_copy_e2e_tests.rb:127 [FINISH] c:0019 p:---- s:0125 e:000124 l:y b:---- CFUNC :load c:0018 p:0006 s:0120 e:000119 l:n b:---- BLOCK /usr/local/bundle/ruby/4.0.0/gems/railties-8.1.3/lib/rails/commands/runner/runner_command.rb:44 c:0017 p:0015 s:0117 e:000116 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/activesupport-8.1.3/lib/active_support/execution_wrapper.rb:91 c:0016 p:0019 s:0109 e:000108 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/railties-8.1.3/lib/rails/commands/runner/runner_command.rb:70 c:0015 p:0090 s:0102 e:000101 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/railties-8.1.3/lib/rails/commands/runner/runner_command.rb:43 c:0014 p:0054 s:0093 e:000092 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/thor-1.5.0/lib/thor/command.rb:28 c:0013 p:0040 s:0085 e:000084 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/thor-1.5.0/lib/thor/invocation.rb:127 c:0012 p:0032 s:0078 e:000077 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/railties-8.1.3/lib/rails/command/base.rb:176 c:0011 p:0246 s:0071 e:000070 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/thor-1.5.0/lib/thor.rb:538 c:0010 p:0049 s:0058 e:000057 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/railties-8.1.3/lib/rails/command/base.rb:71 c:0009 p:0024 s:0051 e:000050 l:n b:---- BLOCK /usr/local/bundle/ruby/4.0.0/gems/railties-8.1.3/lib/rails/command.rb:65 c:0008 p:0015 s:0048 e:000047 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/railties-8.1.3/lib/rails/command.rb:143 c:0007 p:0048 s:0042 e:000041 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/railties-8.1.3/lib/rails/command.rb:63 c:0006 p:0038 s:0031 e:000030 l:y b:0001 TOP /usr/local/bundle/ruby/4.0.0/gems/railties-8.1.3/lib/rails/commands.rb:18 [FINISH] c:0005 p:---- s:0026 e:000025 l:y b:---- CFUNC :require c:0004 p:0033 s:0021 e:000020 l:n b:---- BLOCK /usr/local/lib/ruby/4.0.0/bundled_gems.rb:60 c:0003 p:0145 s:0015 e:000014 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/bootsnap-1.24.4/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:33 c:0002 p:0024 s:0006 e:000005 l:n b:---- EVAL bin/rails:6 [FINISH] c:0001 p:0000 s:0003 E:0019e0 l:y b:---- DUMMY [FINISH] -- Ruby level backtrace information ---------------------------------------- bin/rails:6:in '<main>' /usr/local/bundle/ruby/4.0.0/gems/bootsnap-1.24.4/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:33:in 'require' /usr/local/lib/ruby/4.0.0/bundled_gems.rb:60:in 'block (2 levels) in replace_require' /usr/local/lib/ruby/4.0.0/bundled_gems.rb:60:in 'require' /usr/local/bundle/ruby/4.0.0/gems/railties-8.1.3/lib/rails/commands.rb:18:in '<main>' /usr/local/bundle/ruby/4.0.0/gems/railties-8.1.3/lib/rails/command.rb:63:in 'invoke' /usr/local/bundle/ruby/4.0.0/gems/railties-8.1.3/lib/rails/command.rb:143:in 'with_argv' /usr/local/bundle/ruby/4.0.0/gems/railties-8.1.3/lib/rails/command.rb:65:in 'block in invoke' /usr/local/bundle/ruby/4.0.0/gems/railties-8.1.3/lib/rails/command/base.rb:71:in 'perform' /usr/local/bundle/ruby/4.0.0/gems/thor-1.5.0/lib/thor.rb:538:in 'dispatch' /usr/local/bundle/ruby/4.0.0/gems/railties-8.1.3/lib/rails/command/base.rb:176:in 'invoke_command' /usr/local/bundle/ruby/4.0.0/gems/thor-1.5.0/lib/thor/invocation.rb:127:in 'invoke_command' /usr/local/bundle/ruby/4.0.0/gems/thor-1.5.0/lib/thor/command.rb:28:in 'run' /usr/local/bundle/ruby/4.0.0/gems/railties-8.1.3/lib/rails/commands/runner/runner_command.rb:43:in 'perform' /usr/local/bundle/ruby/4.0.0/gems/railties-8.1.3/lib/rails/commands/runner/runner_command.rb:70:in 'conditional_executor' /usr/local/bundle/ruby/4.0.0/gems/activesupport-8.1.3/lib/active_support/execution_wrapper.rb:91:in 'wrap' /usr/local/bundle/ruby/4.0.0/gems/railties-8.1.3/lib/rails/commands/runner/runner_command.rb:44:in 'block in perform' /usr/local/bundle/ruby/4.0.0/gems/railties-8.1.3/lib/rails/commands/runner/runner_command.rb:44:in 'load' /jeancaisse/spec/account_copy_e2e_tests.rb:127:in '<main>' /usr/local/bundle/ruby/4.0.0/gems/rspec-mocks-3.13.8/lib/rspec/mocks.rb:96:in 'with_temporary_scope' /jeancaisse/spec/account_copy_e2e_tests.rb:128:in 'block in <main>' /jeancaisse/spec/account_copy_e2e_tests.rb:91:in 'run' /usr/local/bundle/ruby/4.0.0/gems/railties-8.1.3/lib/rails/application.rb:556:in 'eager_load!' /usr/local/bundle/ruby/4.0.0/gems/railties-8.1.3/lib/rails/autoloaders.rb:32:in 'each' /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/loader/eager_load.rb:11:in 'eager_load' <internal:thread_sync>:130:in 'synchronize' /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/loader/eager_load.rb:17:in 'block in eager_load' /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/loader/eager_load.rb:17:in 'each' /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/loader/eager_load.rb:18:in 'block (2 levels) in eager_load' /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/loader/eager_load.rb:170:in 'actual_eager_load_dir' /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/loader/file_system.rb:40:in 'ls' <internal:array>:228:in 'each' /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/loader/file_system.rb:51:in 'block in ls' /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/loader/eager_load.rb:175:in 'block in actual_eager_load_dir' /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/cref.rb:62:in 'get' /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/cref.rb:62:in 'const_get' /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/core_ext/kernel.rb:26:in 'require' /usr/local/bundle/ruby/4.0.0/gems/bootsnap-1.24.4/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:33:in 'require' /usr/local/lib/ruby/4.0.0/bundled_gems.rb:60:in 'block (2 levels) in replace_require' /usr/local/lib/ruby/4.0.0/bundled_gems.rb:60:in 'require' /jeancaisse/packs/utils/app/lib/aws/dynamo_d_b.rb:3:in '<main>' /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/core_ext/kernel.rb:34:in 'require' /usr/local/bundle/ruby/4.0.0/gems/bootsnap-1.24.4/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:33:in 'require' /usr/local/lib/ruby/4.0.0/bundled_gems.rb:60:in 'block (2 levels) in replace_require' /usr/local/lib/ruby/4.0.0/bundled_gems.rb:60:in 'require' /usr/local/bundle/ruby/4.0.0/gems/aws-sdk-dynamodb-1.165.0/lib/aws-sdk-dynamodb.rb:63:in '<main>' /usr/local/bundle/ruby/4.0.0/gems/aws-sdk-dynamodb-1.165.0/lib/aws-sdk-dynamodb.rb:63:in 'require_relative' /usr/local/bundle/ruby/4.0.0/gems/aws-sdk-dynamodb-1.165.0/lib/aws-sdk-dynamodb/customizations.rb:4:in '<main>' /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/core_ext/kernel.rb:34:in 'require' /usr/local/bundle/ruby/4.0.0/gems/bootsnap-1.24.4/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:33:in 'require' /usr/local/lib/ruby/4.0.0/bundled_gems.rb:60:in 'block (2 levels) in replace_require' /usr/local/lib/ruby/4.0.0/bundled_gems.rb:60:in 'require' /usr/local/bundle/ruby/4.0.0/gems/aws-sdk-dynamodb-1.165.0/lib/aws-sdk-dynamodb/customizations/client.rb:3:in '<main>' /usr/local/bundle/ruby/4.0.0/gems/aws-sdk-dynamodb-1.165.0/lib/aws-sdk-dynamodb/customizations/client.rb:4:in '<module:Aws>' /usr/local/bundle/ruby/4.0.0/gems/aws-sdk-dynamodb-1.165.0/lib/aws-sdk-dynamodb/customizations/client.rb:5:in '<module:DynamoDB>' /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/core_ext/kernel.rb:34:in 'require' /usr/local/bundle/ruby/4.0.0/gems/bootsnap-1.24.4/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:33:in 'require' /usr/local/lib/ruby/4.0.0/bundled_gems.rb:60:in 'block (2 levels) in replace_require' /usr/local/lib/ruby/4.0.0/bundled_gems.rb:60:in 'require' /usr/local/bundle/ruby/4.0.0/gems/aws-sdk-dynamodb-1.165.0/lib/aws-sdk-dynamodb/client.rb:42:in '<main>' /usr/local/bundle/ruby/4.0.0/gems/aws-sdk-dynamodb-1.165.0/lib/aws-sdk-dynamodb/client.rb:55:in '<module:DynamoDB>' /usr/local/bundle/ruby/4.0.0/gems/aws-sdk-dynamodb-1.165.0/lib/aws-sdk-dynamodb/client.rb:61:in '<class:Client>' /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/core_ext/kernel.rb:34:in 'require' /usr/local/bundle/ruby/4.0.0/gems/bootsnap-1.24.4/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:33:in 'require' /usr/local/lib/ruby/4.0.0/bundled_gems.rb:60:in 'block (2 levels) in replace_require' /usr/local/lib/ruby/4.0.0/bundled_gems.rb:60:in 'require' /usr/local/bundle/ruby/4.0.0/gems/bootsnap-1.24.4/lib/bootsnap/compile_cache/iseq.rb:166:in 'load_iseq' /usr/local/bundle/ruby/4.0.0/gems/bootsnap-1.24.4/lib/bootsnap/compile_cache/iseq.rb:135:in 'fetch' /usr/local/bundle/ruby/4.0.0/gems/bootsnap-1.24.4/lib/bootsnap/compile_cache/iseq.rb:135:in 'fetch' /usr/local/bundle/ruby/4.0.0/gems/bootsnap-1.24.4/lib/bootsnap/compile_cache/iseq.rb:77:in 'input_to_storage' /usr/local/bundle/ruby/4.0.0/gems/bootsnap-1.24.4/lib/bootsnap/compile_cache/iseq.rb:77:in 'compile_file' -- Threading information --------------------------------------------------- Total ractor count: 1 Ruby thread count for this ractor: 3 -- Machine register context ------------------------------------------------ x0: 0x0415f704e8c1b50c x1: 0x30e2222405b75990 x2: 0x4cf5ad432745937f x3: 0x87c37b91114253d5 x4: 0x0000ffffa33963b0 x5: 0x0000000000000000 x6: 0x0000aaaaef82a400 x7: 0x0000aaab1c626b50 x18: 0x0000aaaaef82a778 x19: 0x0000aaab1cc9dff8 x20: 0x0000aaabffa64400 x21: 0x0000ffffde70e050 x22: 0x0000aaaaef830c20 x23: 0x0000ffffa33d5000 x24: 0x0000ffffa2ed3020 x25: 0x0000ffffde70e050 x26: 0x0000aaab1c67d480 x27: 0x0000000000000049 x28: 0x0000000000000001 x29: 0x0000ffffde70dfa0 sp: 0x0000ffffde70dfa0 fau: 0x0000aaab1cc9e000 -- C level backtrace information ------------------------------------------- /usr/local/lib/libruby.so.4.0(fprintf+0x0) [0xffffa2f123f4] /usr/src/ruby/vm_dump.c:1105 /usr/local/lib/libruby.so.4.0(rb_vm_bugreport) /usr/src/ruby/vm_dump.c:1453 /usr/local/lib/libruby.so.4.0(rb_bug_for_fatal_signal+0xd4) [0xffffa2cddc04] /usr/src/ruby/error.c:1131 /usr/local/lib/libruby.so.4.0(sigsegv+0x58) [0xffffa2e48328] /usr/src/ruby/signal.c:948 linux-vdso.so.1(__kernel_rt_sigreturn+0x0) [0xffffa3424838] /usr/local/lib/libruby.so.4.0(vm_ci_hash+0x50) [0xffffa2ed3800] /usr/src/ruby/vm_method.c:632 /usr/local/lib/libruby.so.4.0(normalize_hash_value+0x0) [0xffffa2e546a0] /usr/src/ruby/st.c:331 /usr/local/lib/libruby.so.4.0(do_hash) /usr/src/ruby/st.c:332 /usr/local/lib/libruby.so.4.0(rb_st_update) /usr/src/ruby/st.c:1472 /usr/local/lib/libruby.so.4.0(rb_vm_ci_lookup+0xac) [0xffffa2edd038] /usr/src/ruby/vm_method.c:712 /usr/local/lib/libruby.so.4.0(vm_ci_new_+0x4) [0xffffa2c4c208] /usr/src/ruby/vm_callinfo.h:219 /usr/local/lib/libruby.so.4.0(new_callinfo) /usr/src/ruby/compile.c:1486 /usr/local/lib/libruby.so.4.0(new_insn_send+0xfc) [0xffffa2c4e848] /usr/src/ruby/compile.c:1495 /usr/local/lib/libruby.so.4.0(ADD_ELEM+0x0) [0xffffa2c959d0] /usr/src/ruby/prism_compile.c:3789 /usr/local/lib/libruby.so.4.0(pm_compile_call) /usr/src/ruby/prism_compile.c:3789 /usr/local/lib/libruby.so.4.0(pm_compile_node+0x1218) [0xffffa2c83598] /usr/src/ruby/prism_compile.c:8790 /usr/local/lib/libruby.so.4.0(pm_compile_constant_write_node+0x12c) [0xffffa2c91bcc] /usr/src/ruby/prism_compile.c:5809 /usr/local/lib/libruby.so.4.0(pm_compile_node+0x54c) [0xffffa2c828cc] /usr/src/ruby/prism_compile.c:9055 /usr/local/lib/libruby.so.4.0(pm_compile_node+0x3698) [0xffffa2c85a18] /usr/src/ruby/prism_compile.c:10324 /usr/local/lib/libruby.so.4.0(pm_compile_scope_node+0x1b0c) [0xffffa2c9c974] /usr/src/ruby/prism_compile.c:7044 /usr/local/lib/libruby.so.4.0(pm_compile_node+0x1a00) [0xffffa2c83d80] /usr/src/ruby/prism_compile.c:10197 /usr/local/lib/libruby.so.4.0(pm_iseq_compile_node+0x60) [0xffffa2c9e240] /usr/src/ruby/prism_compile.c:10508 /usr/local/lib/libruby.so.4.0(pm_iseq_new_with_opt_try+0x1c) [0xffffa2d576fc] /usr/src/ruby/iseq.c:1105 /usr/local/lib/libruby.so.4.0(rb_protect+0xb8) [0xffffa2ce9d58] /usr/src/ruby/eval.c:1127 /usr/local/lib/libruby.so.4.0(pm_iseq_new_with_opt+0x150) [0xffffa2d50138] /usr/src/ruby/iseq.c:1158 /usr/local/lib/libruby.so.4.0(pm_new_child_iseq+0xb8) [0xffffa2c4a440] /usr/src/ruby/prism_compile.c:1276 /usr/local/lib/libruby.so.4.0(pm_compile_node+0x328c) [0xffffa2c8560c] /usr/src/ruby/prism_compile.c:9869 /usr/local/lib/libruby.so.4.0(pm_compile_node+0x36c8) [0xffffa2c85a48] /usr/src/ruby/prism_compile.c:10326 /usr/local/lib/libruby.so.4.0(pm_compile_scope_node+0x1b0c) [0xffffa2c9c974] /usr/src/ruby/prism_compile.c:7044 /usr/local/lib/libruby.so.4.0(pm_compile_node+0x1a00) [0xffffa2c83d80] /usr/src/ruby/prism_compile.c:10197 /usr/local/lib/libruby.so.4.0(pm_iseq_compile_node+0x60) [0xffffa2c9e240] /usr/src/ruby/prism_compile.c:10508 /usr/local/lib/libruby.so.4.0(pm_iseq_new_with_opt_try+0x1c) [0xffffa2d576fc] /usr/src/ruby/iseq.c:1105 /usr/local/lib/libruby.so.4.0(rb_protect+0xb8) [0xffffa2ce9d58] /usr/src/ruby/eval.c:1127 /usr/local/lib/libruby.so.4.0(pm_iseq_new_with_opt+0x150) [0xffffa2d50138] /usr/src/ruby/iseq.c:1158 /usr/local/lib/libruby.so.4.0(pm_new_child_iseq+0xb8) [0xffffa2c4a440] /usr/src/ruby/prism_compile.c:1276 /usr/local/lib/libruby.so.4.0(pm_compile_node+0x328c) [0xffffa2c8560c] /usr/src/ruby/prism_compile.c:9869 /usr/local/lib/libruby.so.4.0(pm_compile_node+0x36c8) [0xffffa2c85a48] /usr/src/ruby/prism_compile.c:10326 /usr/local/lib/libruby.so.4.0(pm_compile_scope_node+0x1b0c) [0xffffa2c9c974] /usr/src/ruby/prism_compile.c:7044 /usr/local/lib/libruby.so.4.0(pm_compile_node+0x1a00) [0xffffa2c83d80] /usr/src/ruby/prism_compile.c:10197 /usr/local/lib/libruby.so.4.0(APPEND_LIST+0x0) [0xffffa2c9e2b4] /usr/src/ruby/prism_compile.c:10498 /usr/local/lib/libruby.so.4.0(pm_iseq_compile_node) /usr/src/ruby/prism_compile.c:10502 /usr/local/lib/libruby.so.4.0(pm_iseq_new_with_opt_try+0x1c) [0xffffa2d576fc] /usr/src/ruby/iseq.c:1105 /usr/local/lib/libruby.so.4.0(rb_protect+0xb8) [0xffffa2ce9d58] /usr/src/ruby/eval.c:1127 /usr/local/lib/libruby.so.4.0(pm_iseq_new_with_opt+0x150) [0xffffa2d50138] /usr/src/ruby/iseq.c:1158 /usr/local/lib/libruby.so.4.0(iseqw_s_compile_file_prism+0x1c4) [0xffffa2d5076c] /usr/src/ruby/iseq.c:1925 [0xffff602d3254] ``` **Backtrace 2:** ``` /usr/local/bundle/ruby/4.0.0/gems/aws-sdk-rds-1.314.0/lib/aws-sdk-rds/client_api.rb: [BUG] Segmentation fault at 0x0000aaab3c709000 ruby 4.0.4 (2026-05-12 revision b89eb1bcbf) +YJIT +PRISM [aarch64-linux] -- Control frame information ----------------------------------------------- c:0061 p:---- s:0367 e:000366 l:y b:---- DUMMY [FINISH] c:0060 p:---- s:0364 e:000363 l:y b:---- CFUNC :compile_file c:0059 p:0009 s:0358 e:000357 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/bootsnap-1.24.6/lib/bootsnap/compile_cache/iseq.rb:91 [FINISH] c:0058 p:---- s:0352 e:000351 l:y b:---- CFUNC :fetch c:0057 p:0099 s:0343 e:000342 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/bootsnap-1.24.6/lib/bootsnap/compile_cache/iseq.rb:154 c:0056 p:0008 s:0335 e:000334 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/bootsnap-1.24.6/lib/bootsnap/compile_cache/iseq.rb:185 [FINISH] c:0055 p:---- s:0329 e:000328 l:y b:---- CFUNC :require c:0054 p:0033 s:0324 e:000323 l:n b:---- BLOCK /usr/local/lib/ruby/4.0.0/bundled_gems.rb:60 c:0053 p:0145 s:0318 e:000317 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/bootsnap-1.24.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:33 c:0052 p:0057 s:0309 e:000308 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/core_ext/kernel.rb:34 [FINISH] c:0051 p:0014 s:0301 e:000299 l:y b:0001 CLASS /usr/local/bundle/ruby/4.0.0/gems/aws-sdk-rds-1.314.0/lib/aws-sdk-rds/client.rb:59 c:0050 p:0008 s:0297 e:000296 l:y b:0001 CLASS /usr/local/bundle/ruby/4.0.0/gems/aws-sdk-rds-1.314.0/lib/aws-sdk-rds/client.rb:53 c:0049 p:0181 s:0294 e:000293 l:y b:0001 TOP /usr/local/bundle/ruby/4.0.0/gems/aws-sdk-rds-1.314.0/lib/aws-sdk-rds/client.rb:40 [FINISH] c:0048 p:---- s:0291 e:000290 l:y b:---- CFUNC :require c:0047 p:0033 s:0286 e:000285 l:n b:---- BLOCK /usr/local/lib/ruby/4.0.0/bundled_gems.rb:60 c:0046 p:0145 s:0280 e:000279 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/bootsnap-1.24.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:33 c:0045 p:0057 s:0271 e:000270 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/core_ext/kernel.rb:34 [FINISH] c:0044 p:0017 s:0263 e:000262 l:y b:0001 TOP /jeancaisse/packs/utils/app/lib/aws/rds.rb:12 [FINISH] c:0043 p:---- s:0260 e:000259 l:y b:---- CFUNC :require c:0042 p:0033 s:0255 e:000254 l:n b:---- BLOCK /usr/local/lib/ruby/4.0.0/bundled_gems.rb:60 c:0041 p:0145 s:0249 e:000248 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/bootsnap-1.24.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:33 c:0040 p:0026 s:0240 e:000239 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/core_ext/kernel.rb:26 [FINISH] c:0039 p:---- s:0232 e:000231 l:y b:---- CFUNC :const_get c:0038 p:0010 s:0226 e:000225 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/cref.rb:62 c:0037 p:0039 s:0222 e:000221 l:n b:---- BLOCK /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/loader/eager_load.rb:175 c:0036 p:0063 s:0214 e:000213 l:n b:---- BLOCK /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/loader/file_system.rb:51 [FINISH] c:0035 p:0027 s:0208 e:000207 l:y b:0001 METHOD <internal:array>:228 c:0034 p:0020 s:0202 e:000201 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/loader/file_system.rb:40 c:0033 p:0048 s:0193 e:000192 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/loader/eager_load.rb:170 c:0032 p:0010 s:0182 e:000181 l:n b:---- BLOCK /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/loader/eager_load.rb:18 [FINISH] c:0031 p:---- s:0177 e:000176 l:y b:---- CFUNC :each c:0030 p:0032 s:0173 e:000172 l:n b:---- BLOCK /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/loader/eager_load.rb:17 [FINISH] c:0029 p:0018 s:0170 e:000169 l:y b:0001 METHOD <internal:thread_sync>:130 c:0028 p:0006 s:0166 e:000165 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/loader/eager_load.rb:11 c:0027 p:0005 s:0160 e:000159 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/railties-8.1.3/lib/rails/autoloaders.rb:32 c:0026 p:0009 s:0156 e:000155 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/railties-8.1.3/lib/rails/application.rb:556 c:0025 p:0014 s:0152 e:000151 l:y b:0001 METHOD /jeancaisse/spec/support/eager_load.rb:29 c:0024 p:0132 s:0143 e:000142 l:n b:---- BLOCK /usr/local/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/example_group.rb:273 c:0023 p:0013 s:0132 E:000fa0 l:n b:---- BLOCK /jeancaisse/spec/config/initializers/0_custom_load_hooks_spec.rb:8 [FINISH] c:0022 p:---- s:0129 e:000128 l:y b:---- CFUNC :module_exec c:0021 p:0047 s:0125 e:000124 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/example_group.rb:405 c:0020 p:0012 s:0115 e:000114 l:n b:---- BLOCK /jeancaisse/spec/support/eager_load.rb:30 c:0019 p:0023 s:0112 e:000111 l:y b:0001 METHOD /jeancaisse/spec/support/eager_load.rb:10 c:0018 p:0020 s:0107 e:000106 l:y b:0001 METHOD /jeancaisse/spec/support/eager_load.rb:30 c:0017 p:0132 s:0098 e:000097 l:n b:---- BLOCK /usr/local/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/example_group.rb:273 c:0016 p:0013 s:0087 e:000086 l:n b:---- BLOCK /usr/local/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/dsl.rb:43 c:0015 p:0014 s:0080 e:000079 l:n b:---- BLOCK /usr/local/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/dsl.rb:84 c:0014 p:0006 s:0074 E:000aa0 l:y b:0001 TOP /jeancaisse/spec/config/initializers/0_custom_load_hooks_spec.rb:3 [FINISH] c:0013 p:---- s:0071 e:000070 l:y b:---- CFUNC :load c:0012 p:0007 s:0066 e:000065 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/configuration.rb:2144 c:0011 p:0015 s:0057 e:000056 l:n b:---- BLOCK /usr/local/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/configuration.rb:1643 [FINISH] c:0010 p:0027 s:0052 e:000051 l:y b:0001 METHOD <internal:array>:228 c:0009 p:0017 s:0046 e:000045 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/configuration.rb:1641 c:0008 p:0029 s:0042 e:000041 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/runner.rb:102 c:0007 p:0007 s:0036 e:000035 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/runner.rb:86 c:0006 p:0080 s:0030 e:000029 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/runner.rb:71 c:0005 p:0013 s:0022 e:000021 l:y b:0001 METHOD /usr/local/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/runner.rb:45 c:0004 p:0010 s:0017 e:000016 l:y b:0001 TOP /usr/local/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/exe/rspec:4 [FINISH] c:0003 p:---- s:0014 e:000013 l:y b:---- CFUNC :load c:0002 p:0301 s:0009 E:002438 l:n b:---- EVAL bin/rspec:59 [FINISH] c:0001 p:0000 s:0003 E:001170 l:y b:---- DUMMY [FINISH] -- Ruby level backtrace information ---------------------------------------- bin/rspec:59:in '<main>' bin/rspec:59:in 'load' /usr/local/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/exe/rspec:4:in '<top (required)>' /usr/local/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/runner.rb:45:in 'invoke' /usr/local/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/runner.rb:71:in 'run' /usr/local/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/runner.rb:86:in 'run' /usr/local/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/runner.rb:102:in 'setup' /usr/local/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/configuration.rb:1641:in 'load_spec_files' <internal:array>:228:in 'each' /usr/local/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/configuration.rb:1643:in 'block in load_spec_files' /usr/local/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/configuration.rb:2144:in 'load_file_handling_errors' /usr/local/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/configuration.rb:2144:in 'load' /jeancaisse/spec/config/initializers/0_custom_load_hooks_spec.rb:3:in '<main>' /usr/local/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/dsl.rb:84:in 'block (2 levels) in expose_example_group_alias_globally' /usr/local/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/dsl.rb:43:in 'block in expose_example_group_alias' /usr/local/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/example_group.rb:273:in 'block in define_example_group_method' /jeancaisse/spec/support/eager_load.rb:30:in 'subclass' /jeancaisse/spec/support/eager_load.rb:10:in 'within_eager_load_example_group' /jeancaisse/spec/support/eager_load.rb:30:in 'block in subclass' /usr/local/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/example_group.rb:405:in 'subclass' /usr/local/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/example_group.rb:405:in 'module_exec' /jeancaisse/spec/config/initializers/0_custom_load_hooks_spec.rb:8:in 'block in <main>' /usr/local/bundle/ruby/4.0.0/gems/rspec-core-3.13.6/lib/rspec/core/example_group.rb:273:in 'block in define_example_group_method' /jeancaisse/spec/support/eager_load.rb:29:in 'subclass' /usr/local/bundle/ruby/4.0.0/gems/railties-8.1.3/lib/rails/application.rb:556:in 'eager_load!' /usr/local/bundle/ruby/4.0.0/gems/railties-8.1.3/lib/rails/autoloaders.rb:32:in 'each' /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/loader/eager_load.rb:11:in 'eager_load' <internal:thread_sync>:130:in 'synchronize' /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/loader/eager_load.rb:17:in 'block in eager_load' /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/loader/eager_load.rb:17:in 'each' /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/loader/eager_load.rb:18:in 'block (2 levels) in eager_load' /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/loader/eager_load.rb:170:in 'actual_eager_load_dir' /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/loader/file_system.rb:40:in 'ls' <internal:array>:228:in 'each' /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/loader/file_system.rb:51:in 'block in ls' /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/loader/eager_load.rb:175:in 'block in actual_eager_load_dir' /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/cref.rb:62:in 'get' /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/cref.rb:62:in 'const_get' /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/core_ext/kernel.rb:26:in 'require' /usr/local/bundle/ruby/4.0.0/gems/bootsnap-1.24.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:33:in 'require' /usr/local/lib/ruby/4.0.0/bundled_gems.rb:60:in 'block (2 levels) in replace_require' /usr/local/lib/ruby/4.0.0/bundled_gems.rb:60:in 'require' /jeancaisse/packs/utils/app/lib/aws/rds.rb:12:in '<main>' /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/core_ext/kernel.rb:34:in 'require' /usr/local/bundle/ruby/4.0.0/gems/bootsnap-1.24.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:33:in 'require' /usr/local/lib/ruby/4.0.0/bundled_gems.rb:60:in 'block (2 levels) in replace_require' /usr/local/lib/ruby/4.0.0/bundled_gems.rb:60:in 'require' /usr/local/bundle/ruby/4.0.0/gems/aws-sdk-rds-1.314.0/lib/aws-sdk-rds/client.rb:40:in '<main>' /usr/local/bundle/ruby/4.0.0/gems/aws-sdk-rds-1.314.0/lib/aws-sdk-rds/client.rb:53:in '<module:RDS>' /usr/local/bundle/ruby/4.0.0/gems/aws-sdk-rds-1.314.0/lib/aws-sdk-rds/client.rb:59:in '<class:Client>' /usr/local/bundle/ruby/4.0.0/gems/zeitwerk-2.8.0/lib/zeitwerk/core_ext/kernel.rb:34:in 'require' /usr/local/bundle/ruby/4.0.0/gems/bootsnap-1.24.6/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:33:in 'require' /usr/local/lib/ruby/4.0.0/bundled_gems.rb:60:in 'block (2 levels) in replace_require' /usr/local/lib/ruby/4.0.0/bundled_gems.rb:60:in 'require' /usr/local/bundle/ruby/4.0.0/gems/bootsnap-1.24.6/lib/bootsnap/compile_cache/iseq.rb:185:in 'load_iseq' /usr/local/bundle/ruby/4.0.0/gems/bootsnap-1.24.6/lib/bootsnap/compile_cache/iseq.rb:154:in 'fetch' /usr/local/bundle/ruby/4.0.0/gems/bootsnap-1.24.6/lib/bootsnap/compile_cache/iseq.rb:154:in 'fetch' /usr/local/bundle/ruby/4.0.0/gems/bootsnap-1.24.6/lib/bootsnap/compile_cache/iseq.rb:91:in 'input_to_storage' /usr/local/bundle/ruby/4.0.0/gems/bootsnap-1.24.6/lib/bootsnap/compile_cache/iseq.rb:91:in 'compile_file' -- Threading information --------------------------------------------------- Total ractor count: 1 Ruby thread count for this ractor: 3 -- Machine register context ------------------------------------------------ x0: 0xbd7a2588f4a9410c x1: 0xf19e26916fea2c46 x2: 0x4cf5ad432745937f x3: 0x87c37b91114253d5 x4: 0x0000ffffb68963b0 x5: 0x0000000000000000 x6: 0x0000aaab0d7d0400 x7: 0x0000aaab3c026af0 x18: 0x0000aaab0d7d0778 x19: 0x0000aaab3c708ff8 x20: 0x0000aaad0c2c1180 x21: 0x0000ffffc6ff6dd0 x22: 0x0000aaab0d7d6c20 x23: 0x0000ffffb68d5000 x24: 0x0000ffffb63d3020 x25: 0x0000ffffc6ff6dd0 x26: 0x0000aaab3a3dcf00 x27: 0x0000000000000041 x28: 0x0000000000000001 x29: 0x0000ffffc6ff6d20 sp: 0x0000ffffc6ff6d20 fau: 0x0000aaab3c709000 -- C level backtrace information ------------------------------------------- /usr/local/lib/libruby.so.4.0(fprintf+0x0) [0xffffb64123f4] /usr/src/ruby/vm_dump.c:1105 /usr/local/lib/libruby.so.4.0(rb_vm_bugreport) /usr/src/ruby/vm_dump.c:1453 /usr/local/lib/libruby.so.4.0(rb_bug_for_fatal_signal+0xd4) [0xffffb61ddc04] /usr/src/ruby/error.c:1131 /usr/local/lib/libruby.so.4.0(sigsegv+0x58) [0xffffb6348328] /usr/src/ruby/signal.c:948 linux-vdso.so.1(__kernel_rt_sigreturn+0x0) [0xffffb691b838] /usr/local/lib/libruby.so.4.0(vm_ci_hash+0x50) [0xffffb63d3800] /usr/src/ruby/vm_method.c:632 /usr/local/lib/libruby.so.4.0(normalize_hash_value+0x0) [0xffffb63546a0] /usr/src/ruby/st.c:331 /usr/local/lib/libruby.so.4.0(do_hash) /usr/src/ruby/st.c:332 /usr/local/lib/libruby.so.4.0(rb_st_update) /usr/src/ruby/st.c:1472 /usr/local/lib/libruby.so.4.0(rb_vm_ci_lookup+0xac) [0xffffb63dd038] /usr/src/ruby/vm_method.c:712 /usr/local/lib/libruby.so.4.0(vm_ci_new_+0x4) [0xffffb614c208] /usr/src/ruby/vm_callinfo.h:219 /usr/local/lib/libruby.so.4.0(new_callinfo) /usr/src/ruby/compile.c:1486 /usr/local/lib/libruby.so.4.0(new_insn_send+0xfc) [0xffffb614e848] /usr/src/ruby/compile.c:1495 /usr/local/lib/libruby.so.4.0(pm_compile_call+0x930) [0xffffb6195a58] /usr/src/ruby/prism_compile.c:3794 /usr/local/lib/libruby.so.4.0(pm_compile_node+0x1218) [0xffffb6183598] /usr/src/ruby/prism_compile.c:8790 /usr/local/lib/libruby.so.4.0(pm_setup_args_core+0xe4) [0xffffb6191cf0] /usr/src/ruby/prism_compile.c:1816 /usr/local/lib/libruby.so.4.0(pm_setup_args+0xdc) [0xffffb61927e4] /usr/src/ruby/prism_compile.c:2020 /usr/local/lib/libruby.so.4.0(ISEQ_COMPILE_DATA+0x0) [0xffffb6195210] /usr/src/ruby/prism_compile.c:3706 /usr/local/lib/libruby.so.4.0(pm_compile_call) /usr/src/ruby/prism_compile.c:3707 /usr/local/lib/libruby.so.4.0(pm_compile_node+0x1218) [0xffffb6183598] /usr/src/ruby/prism_compile.c:8790 /usr/local/lib/libruby.so.4.0(pm_compile_node+0x3698) [0xffffb6185a18] /usr/src/ruby/prism_compile.c:10324 /usr/local/lib/libruby.so.4.0(pm_compile_scope_node+0x1b0c) [0xffffb619c974] /usr/src/ruby/prism_compile.c:7044 /usr/local/lib/libruby.so.4.0(pm_compile_node+0x1a00) [0xffffb6183d80] /usr/src/ruby/prism_compile.c:10197 /usr/local/lib/libruby.so.4.0(pm_iseq_compile_node+0x60) [0xffffb619e240] /usr/src/ruby/prism_compile.c:10508 /usr/local/lib/libruby.so.4.0(pm_iseq_new_with_opt_try+0x1c) [0xffffb62576fc] /usr/src/ruby/iseq.c:1105 /usr/local/lib/libruby.so.4.0(rb_protect+0xb8) [0xffffb61e9d58] /usr/src/ruby/eval.c:1127 /usr/local/lib/libruby.so.4.0(pm_iseq_new_with_opt+0x150) [0xffffb6250138] /usr/src/ruby/iseq.c:1158 /usr/local/lib/libruby.so.4.0(pm_new_child_iseq+0xb8) [0xffffb614a440] /usr/src/ruby/prism_compile.c:1276 /usr/local/lib/libruby.so.4.0(pm_compile_node+0x328c) [0xffffb618560c] /usr/src/ruby/prism_compile.c:9869 /usr/local/lib/libruby.so.4.0(pm_compile_node+0x36c8) [0xffffb6185a48] /usr/src/ruby/prism_compile.c:10326 /usr/local/lib/libruby.so.4.0(pm_compile_scope_node+0x1b0c) [0xffffb619c974] /usr/src/ruby/prism_compile.c:7044 /usr/local/lib/libruby.so.4.0(pm_compile_node+0x1a00) [0xffffb6183d80] /usr/src/ruby/prism_compile.c:10197 /usr/local/lib/libruby.so.4.0(pm_iseq_compile_node+0x60) [0xffffb619e240] /usr/src/ruby/prism_compile.c:10508 /usr/local/lib/libruby.so.4.0(pm_iseq_new_with_opt_try+0x1c) [0xffffb62576fc] /usr/src/ruby/iseq.c:1105 /usr/local/lib/libruby.so.4.0(rb_protect+0xb8) [0xffffb61e9d58] /usr/src/ruby/eval.c:1127 /usr/local/lib/libruby.so.4.0(pm_iseq_new_with_opt+0x150) [0xffffb6250138] /usr/src/ruby/iseq.c:1158 /usr/local/lib/libruby.so.4.0(pm_new_child_iseq+0xb8) [0xffffb614a440] /usr/src/ruby/prism_compile.c:1276 /usr/local/lib/libruby.so.4.0(pm_compile_node+0x328c) [0xffffb618560c] /usr/src/ruby/prism_compile.c:9869 /usr/local/lib/libruby.so.4.0(pm_compile_node+0x36c8) [0xffffb6185a48] /usr/src/ruby/prism_compile.c:10326 /usr/local/lib/libruby.so.4.0(pm_compile_scope_node+0x1b0c) [0xffffb619c974] /usr/src/ruby/prism_compile.c:7044 /usr/local/lib/libruby.so.4.0(pm_compile_node+0x1a00) [0xffffb6183d80] /usr/src/ruby/prism_compile.c:10197 /usr/local/lib/libruby.so.4.0(APPEND_LIST+0x0) [0xffffb619e2b4] /usr/src/ruby/prism_compile.c:10498 /usr/local/lib/libruby.so.4.0(pm_iseq_compile_node) /usr/src/ruby/prism_compile.c:10502 /usr/local/lib/libruby.so.4.0(pm_iseq_new_with_opt_try+0x1c) [0xffffb62576fc] /usr/src/ruby/iseq.c:1105 /usr/local/lib/libruby.so.4.0(rb_protect+0xb8) [0xffffb61e9d58] /usr/src/ruby/eval.c:1127 /usr/local/lib/libruby.so.4.0(pm_iseq_new_with_opt+0x150) [0xffffb6250138] /usr/src/ruby/iseq.c:1158 /usr/local/lib/libruby.so.4.0(iseqw_s_compile_file_prism+0x1c4) [0xffffb625076c] /usr/src/ruby/iseq.c:1925 [0xffff77cb7e20] ``` -- https://bugs.ruby-lang.org/

6 17

[ruby-core:124616] [Ruby Bug#21848] GC compaction freezes during code reload with 100% CPU in rb_vm_ci_free -> st_general_delete
by henrik (Henrik A) 27 Jul '26

27 Jul '26

Issue #21848 has been reported by henrik (Henrik A). ---------------------------------------- Bug #21848: GC compaction freezes during code reload with 100% CPU in rb_vm_ci_free -> st_general_delete https://bugs.ruby-lang.org/issues/21848 * Author: henrik (Henrik A) * Status: Open * ruby -v: ruby 4.0.1 (2026-01-13 revision e04267a14b) +PRISM [arm64-darwin24] * Backport: 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN, 4.0: UNKNOWN ---------------------------------------- Ruby 4.0.1 freezes with 100% CPU usage when garbage collection runs during Rails code reloading (hot reload in development). The process becomes unresponsive and requires kill -9 to terminate. Environment: - Ruby: 4.0.1 (Homebrew, ARM64) - Platform: macOS 15.6.1 (Darwin 24.6.0, Apple Silicon) - Rails: 8.x with Puma 7.2.0 - Mode: Development with code reloading enabled Steps to reproduce: 1. Run a Rails application with Puma in development mode (bundle exec rails server -e development -b 0.0.0.0) 2. Make a several code change to trigger hot reload, reload the site in the browser in between 3. Process freezes with ~100% CPU Expected behavior: Code reloads successfully, GC completes normally. Actual behavior: Process freezes indefinitely at 100% CPU. Stack trace from sample shows GC stuck in hash table lookup while freeing VM call info: ``` gc_sweep (in libruby.4.0.dylib) gc_compact_plane gc_sweep_page gc_sweep_plane rb_gc_obj_free_vm_weak_references rb_vm_ci_free st_general_delete find_table_bin_ind vm_ci_hash_cmp <-- stuck here, spinning ``` Full relevant stack (Puma worker thread): ``` Thread: puma srv tp 005 rb_ary_each -> rb_yield -> invoke_block_from_c_bh -> rb_vm_exec -> int_upto -> rb_yield (nested loops) -> vm_search_method_slowpath0 -> rb_vm_search_method_slowpath -> newobj_of -> newobj_cache_miss -> gc_continue -> gc_sweep -> gc_compact_plane -> gc_sweep_page -> gc_sweep_plane -> rb_gc_obj_free_vm_weak_references -> rb_vm_ci_free -> st_general_delete -> find_table_bin_ind -> vm_ci_hash_cmp ``` Workaround: Disabling auto-compaction prevents the freeze: GC.auto_compact = false Analysis: The freeze occurs during GC sweep/compaction when freeing cached VM call info entries (rb_vm_ci_free). This is triggered by code reloading which invalidates method caches. The GC appears to get stuck in an infinite loop or extremely slow operation in find_table_bin_ind while looking up entries in the call info hash table. ---Files-------------------------------- rails_stuck.txt (159 KB) -- https://bugs.ruby-lang.org/

3 3

[ruby-core:116456] [Ruby master Feature#20215] Introduce `IO#readable?`
by ioquatix (Samuel Williams) 25 Jul '26

25 Jul '26

Issue #20215 has been reported by ioquatix (Samuel Williams). ---------------------------------------- Feature #20215: Introduce `IO#readable?` https://bugs.ruby-lang.org/issues/20215 * Author: ioquatix (Samuel Williams) * Status: Open * Priority: Normal ---------------------------------------- There are some cases where, as an optimisation, it's useful to know whether more data is potentially available. We already have `IO#eof?` but the problem with using `IO#eof?` is that it can block indefinitely for sockets. Therefore, code which uses `IO#eof?` to determine if there is potentially more data, may hang. ```ruby def make_request(path = "/") client = connect_remote_host # HTTP/1.0 request: client.write("GET #{path} HTTP/1.0\r\n\r\n") # Read response client.gets("\r\n") # => "HTTP/1.0 200 OK\r\n" # Assuming connection close, there are two things the server can do: # 1. peer.close # 2. peer.write(...); peer.close if client.eof? # <--- Can hang here! puts "Connection closed" # Avoid yielding as we know there definitely won't be any data. else puts "Connection open, data may be available..." # There might be data available, so yield. yield(client) end ensure client&.close end make_request do |client| puts client.read # <--- Prefer to wait here. end ``` The proposed `IO#readable?` is similar to `IO#eof?` but rather than blocking, would simply return false. The expectation is the user will subsequently call `read` which may then wait. The proposed implementation would look something like this: ```ruby class IO def readable? !!self.closed? end end class BasicSocket # Is it likely that the socket is still connected? # May return false positive, but won't return false negative. def readable? return false unless super # If we can wait for the socket to become readable, we know that the socket may still be open. result = self.recv_nonblock(1, MSG_PEEK, exception: false) # No data was available - newer Ruby can return nil instead of empty string: return false if result.nil? # Either there was some data available, or we can wait to see if there is data avaialble. return !result.empty? || result == :wait_readable rescue Errno::ECONNRESET # This might be thrown by recv_nonblock. return false end end ``` For `IO` itself, when there is buffered data, `readable?` would also return true immediately, similar to `eof?`. This is not shown in the above implementation as I'm not sure if there is any Ruby method which exposes "there is buffered data". -- https://bugs.ruby-lang.org/

8 19

[ruby-core:115018] [Ruby master Bug#19922] ObjectSpace.dump_all in multiple threads in parallel causes SEGV
by wanabe (_ wanabe) 20 Jul '26

20 Jul '26

Issue #19922 has been reported by wanabe (_ wanabe). ---------------------------------------- Bug #19922: ObjectSpace.dump_all in multiple threads in parallel causes SEGV https://bugs.ruby-lang.org/issues/19922 * Author: wanabe (_ wanabe) * Status: Open * Priority: Normal * Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- `ObjectSpace.dump_all` in multiple threads in parallel causes SEGV. The reproduce code is here: ``` $ ruby -robjspace -e 'def dump; 10.times { ObjectSpace.dump_all } end; Thread.new { dump }; dump' /home/wanabe/.rbenv/versions/master/lib/ruby/3.3.0+0/objspace.rb:100: [BUG] Segmentation fault at 0x0000000000000000 (snip) ``` I attached the full log. I assumed that: - Thread1 - calls `rb_objspace_reachable_objects_from_root()` - changes `GET_RACTOR()->mfd`: mfd1 - calls `dump_flush()` - changes current thread due to IO - Thread2 - calls `rb_objspace_reachable_objects_from_root()` - changes `GET_RACTOR()->mfd`: mfd2 - calls `dump_flush()` - changes current thread due to IO - Thread1 - gets unexpected `GET_RACTOR()->mfd`: mfd2 ---Files-------------------------------- bug.log (23.1 KB) -- https://bugs.ruby-lang.org/

3 5

[ruby-core:125892] [Ruby Feature#22138] Add `RB_NOGVL_PENDING_INTERRUPT_FAIL` flag for `rb_nogvl`.
by ioquatix (Samuel Williams) 20 Jul '26

20 Jul '26

Issue #22138 has been reported by ioquatix (Samuel Williams). ---------------------------------------- Feature #22138: Add `RB_NOGVL_PENDING_INTERRUPT_FAIL` flag for `rb_nogvl`. https://bugs.ruby-lang.org/issues/22138 * Author: ioquatix (Samuel Williams) * Status: Open ---------------------------------------- Add a new flag, `RB_NOGVL_PENDING_INTERRUPT_FAIL`, to `rb_nogvl()`. When set, `rb_nogvl()` does not enter the blocking region (does not call the supplied function) if the current thread has *pending interrupts* — including interrupts that are currently masked by `Thread.handle_interrupt`. In that case it returns `0` without calling the function, with `errno == 0` — the same as the existing `RB_NOGVL_INTR_FAIL` skip path (the function was never called). This gives selector / event-loop extensions a reliable way to detect that a thread has work to do (a pending interrupt) *before* committing to a potentially unbounded native wait, so they can unwind and let Ruby process the interrupt instead of hanging. ## Background and motivation `rb_nogvl()` already supports a "fail before blocking" mode via `RB_NOGVL_INTR_FAIL` (`0x1`). With that flag, if the VM has been interrupted (`RUBY_VM_INTERRUPTED_ANY`) before the blocking region is entered, the function is skipped and `rb_nogvl()` returns `0`. This is used by `rb_thread_call_without_gvl2()`. However, `RB_NOGVL_INTR_FAIL` only reacts to *deliverable* interrupts. It does not account for interrupts that the current thread has deliberately deferred via `Thread.handle_interrupt`. There is an important class of bugs where: 1. A thread has a pending interrupt (e.g. a `Thread#raise`, a timeout, a shutdown/termination request). 2. That interrupt is masked by an enclosing `Thread.handle_interrupt(... => :never)` / `:on_blocking` region — typical in schedulers, supervisors and connection pools that want to control exactly where interrupts are delivered. 3. The thread is about to enter a native wait (e.g. `kqueue`/`epoll`/`select`, or some other blocking syscall) with the GVL released. 4. Because the interrupt is masked, the existing `RB_NOGVL_INTR_FAIL` check does not trip, the native wait is entered, and — if nothing else wakes it — the wait can block indefinitely. The pending interrupt is never observed. This is not hypothetical: it was hit in production through `async-container` and `io-event`, where a scheduler entering a native selector wait could hang because a pending (masked) interrupt was not noticed before the wait began. A blocking operation that is skipped because the thread has pending work should be treated the same way as an interrupted wait: return immediately without entering the wait, and let the caller unwind so Ruby can process the interrupt. ## Proposal Add the flag: ```c #define RB_NOGVL_PENDING_INTERRUPT_FAIL (0x8) ``` Semantics when the flag is set: - If the current thread has pending interrupts (as reported by the thread's pending-interrupt queue, *including* interrupts masked by `Thread.handle_interrupt`), `rb_nogvl()` does **not** call `func`. It returns `0`. - Otherwise `rb_nogvl()` behaves as usual: it enters the blocking region, calls `func`, and preserves `func`'s resulting `errno`. The check is performed both as an early pre-check (before any of the blocking-region machinery runs) and again inside the blocking-region setup, to close the window between the pre-check and the point where the GVL is released. ## Relationship to existing flags - `RB_NOGVL_INTR_FAIL` (`0x1`) reacts to *deliverable* VM interrupts (`RUBY_VM_INTERRUPTED_ANY`). It does not consider interrupts deferred by `Thread.handle_interrupt`. - `RB_NOGVL_PENDING_INTERRUPT_FAIL` (`0x8`) reacts to *pending* interrupts in the thread's queue, **including masked ones**. This is the key difference: it lets a caller bail out before a native wait even when the interrupt is not currently deliverable, so the caller can unwind to a point where the interrupt can be handled safely. The flags are independent and may be combined with each other and with `RB_NOGVL_UBF_ASYNC_SAFE` / `RB_NOGVL_OFFLOAD_SAFE`. ## Example A common pattern is to have the callback write its result into a struct that is pre-initialised to a sentinel (e.g. `-1`), then report failure once back under the GVL: ```c struct Arguments { int result; }; static void *my_func(void *ptr) { struct Arguments *arguments = ptr; arguments->result = my_syscall(); return NULL; } struct Arguments arguments = {.result = -1}; rb_nogvl(my_func, &arguments, ubf, &arguments, RB_NOGVL_PENDING_INTERRUPT_FAIL); if (arguments.result == -1) { // Either the syscall ran and was interrupted (errno == EINTR), or it was // not run at all because the thread had pending interrupts (errno == 0). rb_sys_fail("my_syscall"); } ``` Note the `errno` caveat for this proposal: on the skip path `errno` is `0`, and `rb_sys_fail()` does not behave well with `errno == 0`. A caller that wants to funnel both cases through `rb_sys_fail()` should normalise it: ```c if (arguments.result == -1) { if (errno == 0) errno = EINTR; // skip path leaves errno == 0 rb_sys_fail("my_syscall"); } ``` See "Errno handling" below for what `errno == EINTR` vs `errno == 0` tells you. Extensions can feature-detect the flag at build time so they keep working on older Rubies: ```c #ifdef RB_NOGVL_PENDING_INTERRUPT_FAIL flags |= RB_NOGVL_PENDING_INTERRUPT_FAIL; #endif ``` ## Errno handling On the pending-interrupt skip path, `rb_nogvl()` returns `0` with `errno == 0`. This matches the existing skip path used by `RB_NOGVL_INTR_FAIL`: when the function is never called, `errno` is restored to its initial value (`0`). The flag does not otherwise change `rb_nogvl()`'s `errno` behaviour, so this change is purely additive and carries no compatibility risk for existing extensions. For a caller, when an operation reports "no result" (e.g. `result == -1`), the two interesting outcomes can be told apart by `errno`: - `errno == EINTR` — the function **did** run and its syscall was actually interrupted (the conventional `EINTR`). Some side effects may have occurred. - `errno == 0` — the function did **not** run: it was skipped before entering the blocking region, either by `RB_NOGVL_PENDING_INTERRUPT_FAIL` (pending, possibly masked, interrupts) or by `RB_NOGVL_INTR_FAIL`. So for this proposal, `result == -1 && (errno == EINTR || errno == 0)` means the operation was not executed, or was interrupted — in both cases the caller should unwind and let Ruby process interrupts. An `errno` of `0` on a skipped callback is admittedly not very ergonomic (it forces the `if (errno == 0) errno = EINTR;` dance above before `rb_sys_fail()`). Making the skip paths report `EINTR` directly would remove that wrinkle, but it also erases the `EINTR`-vs-`0` distinction above (you could no longer tell a truly-interrupted syscall from a never-run one). That trade-off is a separate concern and may be proposed independently; this proposal keeps the existing behaviour and stays focused on the new flag. ## Implementation A reference implementation is available: - `RB_NOGVL_PENDING_INTERRUPT_FAIL` flag: <https://github.com/ruby/ruby/pull/17553> Downstream user with feature detection and a fallback for older Rubies: - io-event: <https://github.com/socketry/io-event/pull/197> The focused CRuby C-API specs (`spec/ruby/optional/capi/thread_spec.rb`) cover the new flag: the function is not called when the current thread has masked pending interrupts, and `errno` is `0`. -- https://bugs.ruby-lang.org/

1 2

[ruby-core:125882] [Ruby Feature#22135] Remove deprecated `ObjectSpace#_id2ref`
by nobu (Nobuyoshi Nakada) 17 Jul '26

17 Jul '26

Issue #22135 has been reported by nobu (Nobuyoshi Nakada). ---------------------------------------- Feature #22135: Remove deprecated `ObjectSpace#_id2ref` https://bugs.ruby-lang.org/issues/22135 * Author: nobu (Nobuyoshi Nakada) * Status: Open ---------------------------------------- As a result of [Feature #15408], the `ObjectSpace#_id2ref` method has been deprecated and now triggers a warning. However, we recognize that its use had already been discouraged for a long time prior to this, and we believe it is rarely used nowadays. Are there any objections to removing this method in version 4.1? [GH-17577](https://github.com/ruby/ruby/pull/17577) -- https://bugs.ruby-lang.org/

8 7

[ruby-core:125722] [Ruby Feature#22108] Computed hash keys with (expr): syntax
by yertto (_ yertto) 16 Jul '26

16 Jul '26

Issue #22108 has been reported by yertto (_ yertto). ---------------------------------------- Feature #22108: Computed hash keys with (expr): syntax https://bugs.ruby-lang.org/issues/22108 * Author: yertto (_ yertto) * Status: Open ---------------------------------------- # Computed hash keys with `(expr):` syntax Allow `{ (expr): value }` as a computed hash key. Almost 20 years in the making, the missing puzzle piece for Hash's "new" colon notation: ```ruby h = { name: "symbol shorthand", # Ruby 1.9+ "quoted label": "symbol label", # Ruby 2.2+ (Feature #4935) (expr): "computed", # THIS PROPOSAL } ``` ## Motivation Ruby has long had two colon-based hash key syntaxes (name: for symbol keys and "quoted label": for quoted symbol keys). Adding (expr): is a baby step toward allowing all-colon hashes: ```ruby # Before -- mixed styles { name: "Alice", role: "admin", "key-#{n}": value, n => value } # After -- uniform colon syntax { name: "Alice", role: "admin", ("key-#{n}"): value, (n): value } ``` (And maybe a step closer to one day retiring the "hash rocket" `=>` from Hashes entirely?) ### Completing the colon family | Example | Since Ruby | Key type | |---------|-------|----------| | `{ name: value }` | [v1.9](https://docs.ruby-lang.org/en/3.4/NEWS/NEWS-1_9_1.html) | Symbol | | `{ "quoted label": value }` | [v2.2](https://docs.ruby-lang.org/en/3.4/NEWS/NEWS-2_2_0.html) | Symbol (quoted label) | | `{ (expr): value }` | *???* | Runtime expression value | ### Readability for computed-key-heavy code Code that builds dynamic hashes currently forces a style break midway through a literal. This is especially noticeable with interpolated keys, numeric keys, or variable-driven keys. ### Reducing `=>` overloading The `=>` token has been used to serve more purposes than the Hash literal (aka "Hash rocket") it was originally used for. - rightward assignment ``` expr => var ``` - pattern capture ``` case {name: "Alice", role: "admin"} in {name: String => name, role:} # capture the name String value into `name` p name # => "Alice" end ``` - rescue variables ``` rescue SomeExceptionClass => e ``` ``` rescue => e ``` Reducing its use in Hashes simplifies the language, especially for newcomers. ## Design ### `(expr):` vs `[expr]:` Parenthesized expressions were chosen over square bracket delimited: - Idempotent wrapping: `((x))` = `(x)`, but `[[x]]` != `[x]` (nested array) - Array keys: `{(["a"]): "b"}` reads naturally vs `{[["a"]]: "b"}` requiring extra wrapping - [jq precedent](https://jqlang.org/manual/v1.6/#object-construction): the JSON query language uses identical `{("a"+"b"): 59}` syntax (since jq 1.6, 2018) - Parentheses signals a grouping or "evaluate this", whereas square brackets signals an Array/container ### Improving on JavaScript JavaScript's "computed property names" `{ [expr]: value }` were introduced in ECMAScript 2015 (ES6), 3 years before the jq version. In Ruby, `[]` already means Array literal and method call. Rather than overloading `[]` further, `(expr):` (from jq) improves on the JavaScript design. Parentheses naturally signal evaluation, `):` inside `{}` is unambiguous to the lexer, and it matches the well-established jq convention. ### Edge cases handled - `(expr) : value` (space before colon) -- *syntax error* (consistent with `name : value`) - `{ (expr): }` (value omission) -- *syntax error* (runtime expression, no compile-time local to infer) - Mixed styles: `{ (1): "one", two: "two", "three": "three" }` -- *valid* - Nested parens: `{ ((1 + 2) * 3): "nested" }` -- *valid* - Nested hashes: `{ ({(1): "one"}): "two" }` -- *valid* ## Implementation Three changes to `parse.y` (Lrama LALR(1) parser, zero new conflicts): 1. Lexer: emit `tLABEL_END` when `EXPR_ENDFN` state, no space before `:`, and inside `brace_nest > 0` 2. Grammar: new `assoc` alternative -- `tLPAREN compstmt ")" tLABEL_END arg_value` 3. Precedence: `%nonassoc ')'` to disambiguate Reference implementation: [feature/computed-hash-keys](https://github.com/ruby/ruby/pull/17299) PR on GitHub. ## Historical context This was discussed on ruby-core in October 2007 (["General hash keys for colon notation"](https://public-inbox.org/ruby-core/E1ImQBE-00033s-IZ@x31/T/), murphy). Withdrawn due to the 1.9 feature freeze. Since then, `"quoted label":` (Ruby 2.2, [Feature #4935](https://bugs.ruby-lang.org/issues/4935)) and value omission (Ruby 3.1, [Feature #14579](https://bugs.ruby-lang.org/issues/14579)) have expanded the colon family, making the computed-key gap more conspicuous. Meanwhile, jq introduced the identical `{("a"+"b"):59}` syntax in jq 1.6 (2018), demonstrating real-world viability. ## Open questions - Is this syntax acceptable to the community? - Ripper (Ruby's parser library) does not yet emit events for this syntax -- should that be added before merging, or can it follow separately? - Is the jq precedent compelling enough to address the "no language does this" objection? ## Future directions All colon-based key syntaxes would now be available. This opens up the possibility of eventually deprecating `=>` from Hash literals (while keeping it for rescue, pattern matching, and rightward assignment). This proposal does not require that change - it is simply the enabling step, and any deprecation timeline could be a separate discussion. -- https://bugs.ruby-lang.org/

4 10

[ruby-core:125045] [Ruby Bug#21955] `Fiber#transfer`: machine stack not released when fiber terminates, causing `FiberError: can't set a guard page`
by ioquatix (Samuel Williams) 15 Jul '26

15 Jul '26

Issue #21955 has been reported by ioquatix (Samuel Williams). ---------------------------------------- Bug #21955: `Fiber#transfer`: machine stack not released when fiber terminates, causing `FiberError: can't set a guard page` https://bugs.ruby-lang.org/issues/21955 * Author: ioquatix (Samuel Williams) * Status: Open * Assignee: ioquatix (Samuel Williams) * Backport: 3.2: REQUIRED, 3.3: REQUIRED, 3.4: REQUIRED, 4.0: REQUIRED ---------------------------------------- When a fiber terminates (falls off the end of its block, or raises an unhandled exception) after being reached via `Fiber#transfer`, its machine stack is **not** returned to the fiber pool. The stack is only freed when the `Fiber` object is eventually garbage collected. In production, where GC does not run continuously, terminated fibers accumulate unreleased stacks. Each stack allocation contains a guard page set with `mprotect(PROT_NONE)`, which splits a kernel VMA. On Linux this exhausts the per-process `vm.max_map_count` limit and raises: ``` FiberError: can't set a guard page: Cannot allocate memory ``` The symptom is confusing: the fibers are all dead (`alive? == false`), new fibers cannot be created, but GC has not run. ## Root cause In `cont.c`, `fiber_switch()`, the eager stack release after `fiber_store` returns is guarded by `resuming_fiber`: ```c // cont.c (affected versions) #ifndef COROUTINE_PTHREAD_CONTEXT if (resuming_fiber && FIBER_TERMINATED_P(fiber)) { RB_VM_LOCKING() { fiber_stack_release(fiber); } } #endif ``` `resuming_fiber` is only non-`NULL` when the switch was initiated by `Fiber#resume` (which passes `resuming_fiber = fiber`). `Fiber#transfer` passes `resuming_fiber = NULL`, so the condition is never true and the stack is silently leaked until GC. Additionally, `fiber_raise` on a suspended non-yielding (transferred) fiber calls `fiber_transfer_kw`, also passing `resuming_fiber = NULL`, so the same leak occurs when a transferred fiber is terminated by a raised exception. ## Reproduction Set a low map count limit, then run the attached script: ``` sudo bash -c "echo 10000 > /proc/sys/vm/max_map_count" ruby test_fiber_transfer_leak.rb ``` Restore afterwards (`sysctl vm.max_map_count` shows the default, typically 65530). ```ruby GC.disable leaked = [] count = 0 begin 10_000.times do f = Fiber.new { } # terminates immediately leaked << f # hold reference so Fiber object is not GC'd f.transfer # transfer, not resume => stack NOT released (bug) count += 1 puts "[#{count} fibers] all dead: #{leaked.none?(&:alive?)}" if count % 1000 == 0 end puts "No error — fix is applied." rescue FiberError => e puts "FiberError after #{count} fibers: #{e.message}" puts "All terminated (alive?=false): #{leaked.none?(&:alive?)}" ensure GC.enable leaked.clear GC.start end ``` Expected output on **unpatched** Ruby (vm.max_map_count=10000): ``` [1000 fibers] all dead: true [2000 fibers] all dead: true [3000 fibers] all dead: true [4000 fibers] all dead: true FiberError after 4096 fibers: can't set a guard page: Cannot allocate memory All terminated (alive?=false): false ``` Expected output on **patched** Ruby: ``` [1000 fibers] all dead: true ... [10000 fibers] all dead: true No error — fix is applied. ``` ## Fix Drop the `resuming_fiber &&` guard. After `fiber_store` returns we are executing in the caller's context — we are never on `fiber`'s stack — so releasing it is unconditionally safe. `fiber_stack_release` is already idempotent (guarded by `fiber->stack.base == NULL`), so the resume path is unaffected. ```c #ifndef COROUTINE_PTHREAD_CONTEXT if (FIBER_TERMINATED_P(fiber)) { RB_VM_LOCKING() { fiber_stack_release(fiber); } } #endif ``` Pull request with fix: https://github.com/ruby/ruby/pull/16416 -- https://bugs.ruby-lang.org/

4 3

[ruby-core:113743] [Ruby master Feature#19708] Support `attr_reader :foo?`
by AMomchilov (Alexander Momchilov) 13 Jul '26

13 Jul '26

Issue #19708 has been reported by AMomchilov (Alexander Momchilov). ---------------------------------------- Feature #19708: Support `attr_reader :foo?` https://bugs.ruby-lang.org/issues/19708 * Author: AMomchilov (Alexander Momchilov) * Status: Open * Priority: Normal ---------------------------------------- Creating reader methods with `attr_reader` is preferable over defining them by hand, not only because it's more convenient, but also because it hits a fast path in MRI (see `VM_METHOD_TYPE_IVAR`). Since local and instance variables can't end with `?`, you can't use `attr_reader` to define predicate-style methods for boolean values, like: ```ruby class Person attr_reader(:name, :age, :active?) # invalid attribute name `active?' (NameError) def initialize @name = "Bob" @age = 30 @active = true end end ``` It would be nice if `attr_reader` (and friends) could behave like: ```ruby def active? = @active ``` (`attr_writer` and `attr_accessor` couldn't do the same, since `def active?=(new_value)` isn't valid, so they'd probably stick with `def active=(new_value)`) -- https://bugs.ruby-lang.org/

5 7

[ruby-core:125428] [Ruby Bug#22058] {Method,InstanceMethod}#super_method doesn't work correctly for refined method with refinements for method active in the caller's scope
by jeremyevans0 (Jeremy Evans) 12 Jul '26

12 Jul '26

Issue #22058 has been reported by jeremyevans0 (Jeremy Evans). ---------------------------------------- Bug #22058: {Method,InstanceMethod}#super_method doesn't work correctly for refined method with refinements for method active in the caller's scope https://bugs.ruby-lang.org/issues/22058 * Author: jeremyevans0 (Jeremy Evans) * Status: Open * ruby -v: ruby 4.1.0dev (2026-05-03T23:57:21Z master d8d2ed5dc9) +PRISM [x86_64-openbsd7.8] * Backport: 3.3: UNKNOWN, 3.4: UNKNOWN, 4.0: UNKNOWN ---------------------------------------- I've found that Method#super_method and InstanceMethod#super_method do not work correctly in some cases for refined methods. At the least, there is a definite bug, which is that #super_method inside a scope with a refinement activated for the method results in a loop over the refined methods. I'm not sure if the semantics for #super_method for refined methods were ever discussed. Other than the bug regarding the loop over the refinement, the currently semantics seem to be: * While handling additional refined methods for the same class as the current method, #super_method will consider the refinements active at the point the method was created * For ancestors, #super_method will consider the refinements active in the scope calling #super_method These semantics seem questionable. My guess is they are not the result of intentional design, but due purely to implementation details. I see two possibilities: 1. Keep the current behavior, where results depend on refinements activated in the caller's namespace. In this case, I recommend that we not have different handling when there are other refinements for the same class as the current method should. If refinements are not in scope, #super_method should not return them. We should also consider whether #super_method should error if the receiver is a refinement method for a refinement not activated in the caller's scope. 2. Change #super_method so that it depends on the refinements activated in the namespace it was created in, for ancestors as well as for the current class. This would make #super_method return the same result no matter where it was called. I think option 2 makes more sense, but it requires that Method/InstanceMethod objects for refined methods keep a reference to the scope in which they were created. A related minor bug I found during this research is the #inspect output for #super_method results for refined methods also does not use the same format, indicating there is something internally different. Here's example code showing these issues, with commented output below: ```ruby class B def b = 16 end class A < B def b = 8 + super end module M1 refine(A){def b = 1 + super} end module M2 refine(A){def b = 2 + super} end module M3 refine(A){def b = 4 + super} end module M4 refine(B){def b = 4 + super} end I = A.new.method(:b) C = A.instance_method(:b) module N0 using M1 using M3 I = A.new.method(:b) C = A.instance_method(:b) end module N using M1 using M2 using M3 using M4 I = A.new.method(:b) C = A.instance_method(:b) puts "", "Inside module using all refinements using method created using all refinements:" p I i = I 6.times do i = i.super_method p i end puts p C c = C 6.times do c = c.super_method p c end puts "", "Inside module using all refinements using method created using some refinements:" p N0::I i = N0::I 6.times do i = i.super_method p i end puts p N0::C c = N0::C 6.times do c = c.super_method p c end puts "", "Inside module using all refinements using method created using no refinements:" p ::I i = ::I 6.times do break unless i = i.super_method p i end puts p ::C c = ::C 6.times do break unless c = c.super_method p c end end module N0 using M1 using M3 puts "", "Inside module using some refinements using method created using all refinements:" p N::I i = N::I 6.times do break unless i = i.super_method p i end puts p N::C c = N::C 6.times do break unless c = c.super_method p c end end puts "", "Top level using method created with all refinements:" p N::I i = N::I 6.times do break unless i = i.super_method p i end puts p N::C c = N::C 6.times do break unless c = c.super_method p c end puts "", "Top level using method created with some refinements:" p N0::I i = N0::I 6.times do break unless i = i.super_method p i end puts p N0::C c = N0::C 6.times do break unless c = c.super_method p c end puts "", "Top level using method created with no refinements:" p I i = I 6.times do break unless i = i.super_method p i end puts p C c = C 6.times do break unless c = c.super_method p c end ``` First, the bug. This shows a loop among active refinements. After going through M3, M2, and M1, it loops back to M3. This also shows weird #inspect output, with #super_method not showing the main class. ``` Inside module using all refinements using method created using all refinements: #<Method: A(#<refinement:A@M3>)#b() t/t43.rb:42> #<Method: #<refinement:A@M2>#b() t/t43.rb:38> #<Method: #<refinement:A@M1>#b() t/t43.rb:34> #<Method: #<refinement:A@M3>#b() t/t43.rb:42> #<Method: #<refinement:A@M2>#b() t/t43.rb:38> #<Method: #<refinement:A@M1>#b() t/t43.rb:34> #<Method: #<refinement:A@M3>#b() t/t43.rb:42> #<UnboundMethod: #<refinement:A@M3>#b() t/t43.rb:42> #<UnboundMethod: #<refinement:A@M2>#b() t/t43.rb:38> #<UnboundMethod: #<refinement:A@M1>#b() t/t43.rb:34> #<UnboundMethod: #<refinement:A@M3>#b() t/t43.rb:42> #<UnboundMethod: #<refinement:A@M2>#b() t/t43.rb:38> #<UnboundMethod: #<refinement:A@M1>#b() t/t43.rb:34> #<UnboundMethod: #<refinement:A@M3>#b() t/t43.rb:42> ``` This shows the dynamic scoping of the #super_method. At time of call, only M3 and M1 are in scope. You see in the first loop, only M3 and M1 are used, but subsequent loops use M3, M2, and M1. ``` Inside module using all refinements using method created using some refinements: #<Method: A(#<refinement:A@M3>)#b() t/t43.rb:42> #<Method: #<refinement:A@M1>#b() t/t43.rb:34> #<Method: #<refinement:A@M3>#b() t/t43.rb:42> #<Method: #<refinement:A@M2>#b() t/t43.rb:38> #<Method: #<refinement:A@M1>#b() t/t43.rb:34> #<Method: #<refinement:A@M3>#b() t/t43.rb:42> #<Method: #<refinement:A@M2>#b() t/t43.rb:38> #<UnboundMethod: #<refinement:A@M3>#b() t/t43.rb:42> #<UnboundMethod: #<refinement:A@M1>#b() t/t43.rb:34> #<UnboundMethod: #<refinement:A@M3>#b() t/t43.rb:42> #<UnboundMethod: #<refinement:A@M2>#b() t/t43.rb:38> #<UnboundMethod: #<refinement:A@M1>#b() t/t43.rb:34> #<UnboundMethod: #<refinement:A@M3>#b() t/t43.rb:42> #<UnboundMethod: #<refinement:A@M2>#b() t/t43.rb:38> ``` This shows a case where the Method was created with no refinements activated. Refinements for superclasses that are active in the current scope are still picked up: ``` Inside module using all refinements using method created using no refinements: #<Method: A#b() t/t43.rb:30> #<Method: #<refinement:B@M4>#b() t/t43.rb:46> #<Method: #<refinement:B@M4>#b() t/t43.rb:46> #<Method: #<refinement:B@M4>#b() t/t43.rb:46> #<Method: #<refinement:B@M4>#b() t/t43.rb:46> #<Method: #<refinement:B@M4>#b() t/t43.rb:46> #<Method: #<refinement:B@M4>#b() t/t43.rb:46> #<UnboundMethod: A#b() t/t43.rb:30> #<UnboundMethod: #<refinement:B@M4>#b() t/t43.rb:46> #<UnboundMethod: #<refinement:B@M4>#b() t/t43.rb:46> #<UnboundMethod: #<refinement:B@M4>#b() t/t43.rb:46> #<UnboundMethod: #<refinement:B@M4>#b() t/t43.rb:46> #<UnboundMethod: #<refinement:B@M4>#b() t/t43.rb:46> #<UnboundMethod: #<refinement:B@M4>#b() t/t43.rb:46> ``` More evidence for dynamic scoping. This is the opposite of the second example, where the first loop has M3, M2, and M1, and subsequent loops have M3 and M1. ``` Inside module using some refinements using method created using all refinements: #<Method: A(#<refinement:A@M3>)#b() t/t43.rb:42> #<Method: #<refinement:A@M2>#b() t/t43.rb:38> #<Method: #<refinement:A@M1>#b() t/t43.rb:34> #<Method: #<refinement:A@M3>#b() t/t43.rb:42> #<Method: #<refinement:A@M1>#b() t/t43.rb:34> #<Method: #<refinement:A@M3>#b() t/t43.rb:42> #<Method: #<refinement:A@M1>#b() t/t43.rb:34> #<UnboundMethod: #<refinement:A@M3>#b() t/t43.rb:42> #<UnboundMethod: #<refinement:A@M2>#b() t/t43.rb:38> #<UnboundMethod: #<refinement:A@M1>#b() t/t43.rb:34> #<UnboundMethod: #<refinement:A@M3>#b() t/t43.rb:42> #<UnboundMethod: #<refinement:A@M1>#b() t/t43.rb:34> #<UnboundMethod: #<refinement:A@M3>#b() t/t43.rb:42> #<UnboundMethod: #<refinement:A@M1>#b() t/t43.rb:34> ``` This shows the behavior when no refinements are activated in the current scope. It still includes refinements for the same class as the current method, but no refinements for superclasses. Also, note that there is no longer a loop, because there are no refinements activated: ``` Top level using method created with all refinements: #<Method: A(#<refinement:A@M3>)#b() t/t43.rb:42> #<Method: #<refinement:A@M2>#b() t/t43.rb:38> #<Method: #<refinement:A@M1>#b() t/t43.rb:34> #<Method: A#b() t/t43.rb:30> #<Method: B#b() t/t43.rb:26> #<UnboundMethod: #<refinement:A@M3>#b() t/t43.rb:42> #<UnboundMethod: #<refinement:A@M2>#b() t/t43.rb:38> #<UnboundMethod: #<refinement:A@M1>#b() t/t43.rb:34> #<UnboundMethod: A#b() t/t43.rb:30> #<UnboundMethod: B#b() t/t43.rb:26> ``` This shows that only the refinements were activated at the point the method was created are included. ``` Top level using method created with some refinements: #<Method: A(#<refinement:A@M3>)#b() t/t43.rb:42> #<Method: #<refinement:A@M1>#b() t/t43.rb:34> #<Method: A#b() t/t43.rb:30> #<Method: B#b() t/t43.rb:26> #<UnboundMethod: #<refinement:A@M3>#b() t/t43.rb:42> #<UnboundMethod: #<refinement:A@M1>#b() t/t43.rb:34> #<UnboundMethod: A#b() t/t43.rb:30> #<UnboundMethod: B#b() t/t43.rb:26> ``` This output doesn't show any problems, it shows that if refinements were not activated when the method was created, and are not activated when #super_method is called, that #super_method ignores refinements, which is what you would expect. ``` Top level using method created with no refinements: #<Method: A#b() t/t43.rb:30> #<Method: B#b() t/t43.rb:26> #<UnboundMethod: A#b() t/t43.rb:30> #<UnboundMethod: B#b() t/t43.rb:26> ``` -- https://bugs.ruby-lang.org/

4 15