Bug #21191: Ruby 3.4.2 crashes unexpectedly

• Status: Feedback
• Assignee: -
• Target version: -
• ruby -v: ruby 3.4.2 (2025-02-15 revision d2930f8e7a) +PRISM [arm64-darwin24]
• Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN

[datanoise (Kent Sibilev)]

Running my Rails app in development mode with Ruby 3.4.2 crashes with:

Thread 15 Crashed:: puma srv tp 003
0 libsystem_kernel.dylib 0x19323f720 __pthread_kill + 8
1 libsystem_pthread.dylib 0x193277f70 pthread_kill + 288
2 libsystem_c.dylib 0x193184908 abort + 128
3 libruby.3.4.dylib 0x10176c30c die + 12
4 libruby.3.4.dylib 0x101a78e38 rb_bug + 32
5 libruby.3.4.dylib 0x101a49570 yjit::yjit::rb_bug_panic_hook::$u7b$$u7b$closure$u7d$$u7d$::h0f4c55d7c8e55fcf + 340
6 libruby.3.4.dylib 0x1019d242c std::panicking::rust_panic_with_hook::h9a5dc30b684e2ff4 + 740
7 libruby.3.4.dylib 0x1019d2030 std::panicking::begin_panic_handler::$u7b$$u7b$closure$u7d$$u7d$::hbcb5de8b840ae91c + 104
8 libruby.3.4.dylib 0x1019d1188 std::sys::backtrace::__rust_end_short_backtrace::ha657d4b4d65dc993 + 12
9 libruby.3.4.dylib 0x1019d1cdc rust_begin_unwind + 32
10 libruby.3.4.dylib 0x101a6a8c8 core::panicking::panic_fmt::hda207213c7ca0065 + 32
11 libruby.3.4.dylib 0x101a6a938 core::panicking::panic::h58f3db1cc4835fac + 52
12 libruby.3.4.dylib 0x1019f3330 yjit::codegen::jit_guard_known_klass::h231d0cbaae1c099c + 2852
13 libruby.3.4.dylib 0x1019ec404 yjit::codegen::gen_equality_specialized::h93a21f50d2816872 + 760
14 libruby.3.4.dylib 0x1019ec82c yjit::codegen::gen_opt_eq::h5396bf9fac489b74 + 36
15 libruby.3.4.dylib 0x1019df604 yjit::codegen::gen_single_block::h01cba096a3e9933d + 2996
16 libruby.3.4.dylib 0x101a200a8 yjit::core::gen_block_series::h1b8008b9e695e93a + 132
17 libruby.3.4.dylib 0x101a21fe0 yjit::core::branch_stub_hit_body::ha9f3b0e799953b26 + 916
18 libruby.3.4.dylib 0x101a3a390 yjit::stats::with_compile_time::hb64811b90dfb965e + 64
19 libruby.3.4.dylib 0x101a66088 yjit::cruby::with_vm_lock::hf301ea5cad023986 + 84
20 libruby.3.4.dylib 0x101a253e4 yjit::core::branch_stub_hit::h44174fb9640d7093 + 80
21 ??? 0x150002078 ???
22 libruby.3.4.dylib 0x10190ad58 vm_exec_core + 9576
23 libruby.3.4.dylib 0x1019072d8 rb_vm_exec + 492
24 libruby.3.4.dylib 0x10192ed2c invoke_block_from_c_bh + 872
25 libruby.3.4.dylib 0x10192e46c catch_i + 108
26 libruby.3.4.dylib 0x101918e78 vm_catch_protect + 200
27 libruby.3.4.dylib 0x101919888 rb_f_catch + 112
28 ??? 0x1502acbe4 ???
29 libruby.3.4.dylib 0x10190ad58 vm_exec_core + 9576
30 libruby.3.4.dylib 0x101907304 rb_vm_exec + 536
31 libruby.3.4.dylib 0x10191ba24 vm_invoke_proc + 712
32 libruby.3.4.dylib 0x1018db74c thread_do_start_proc + 668
33 libruby.3.4.dylib 0x1018dae18 thread_start_func_2 + 796
34 libruby.3.4.dylib 0x1018da994 nt_start + 248
35 libsystem_pthread.dylib 0x1932782e4 _pthread_start + 136
36 libsystem_pthread.dylib 0x1932730fc thread_start + 8

[alanwu (Alan Wu)]

• Status changed from Open to Feedback

Would you mind posting the report generated with RUBY_CRASH_REPORT? (See man ruby.)