Issue #21004 has been updated by peterzhu2118 (Peter Zhu). Backport changed from 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN to 3.1: DONTNEED, 3.2: DONTNEED, 3.3: DONTNEED, 3.4: DONTNEED I have a fix here: https://github.com/ruby/ruby/pull/12508 ---------------------------------------- Bug #21004: Memory leak with `new_locations_lambda_body` https://bugs.ruby-lang.org/issues/21004#change-111262 * Author: kddnewton (Kevin Newton) * Status: Open * Backport: 3.1: DONTNEED, 3.2: DONTNEED, 3.3: DONTNEED, 3.4: DONTNEED ---------------------------------------- You can find the valgrind output here: https://github.com/ruby/prism/actions/runs/12613463262/job/35151355503?pr=33.... It looks like the allocated lambda locations are leaking under certain circumstances. The leak looks to be introduced here: https://github.com/ruby/ruby/commit/fa2517451ec. -- https://bugs.ruby-lang.org/