Issue #19299 has been updated by alanwu (Alan Wu). Thank you for the report! I was able to reproduce the issue with the logs you posted, so no worries about reducing your app. It happens with `yield` and a block with a lot of local variables and it should be specific to ARM: ```ruby def foo yield end 30.times do foo do a1=a2=a3=a4=a5=a6=a7=a8=a9=a10=a11=a12=a13=a14=a15=a16=a17=a18=a19=a20=a21=a22=a23=a24=a25=a26=a27=a28=a29=a30 = 0 end end ``` I submitted a [PR](https://github.com/ruby/ruby/pull/7059) to fix this issue. ---------------------------------------- Bug #19299: YJIT panicked while holding VM lock acquired at ./yjit/src/core.rs:1693. Aborting... https://bugs.ruby-lang.org/issues/19299#change-100978 * Author: ollym (Oliver Morgan) * Status: Open * Priority: Normal * ruby -v: ruby 3.2.0 (2022-12-25 revision a528908271) +YJIT [arm64-darwin22] * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- Attached is the backtrace. The code is a moderately complex view with partials and translations. The panic happens specifically when i call a translation `t('...')` but if i simplify the view code around that call the panic goes away. I'm trying to create a simplified way to recreate it without giving you the full application. I'll keep trying, unless the backtrace is enough. ---Files-------------------------------- backtrace.txt (12.3 KB) -- https://bugs.ruby-lang.org/