From: "naruse (Yui NARUSE) via ruby-core" Date: 2024-03-20T12:58:24+00:00 Subject: [ruby-core:117261] [Ruby master Bug#20209] YJIT can leak memory by retaining objects with singleton class Issue #20209 has been updated by naruse (Yui NARUSE). Backport changed from 3.0: DONTNEED, 3.1: DONTNEED, 3.2: DONTNEED, 3.3: REQUIRED to 3.0: DONTNEED, 3.1: DONTNEED, 3.2: DONTNEED, 3.3: DONE ruby_3_3 cdcabd8a44ee2f4a2b549a3460a5c77c2dffca36 merged revision(s) 2cc7a56e,b0711b1,db5d9429. ---------------------------------------- Bug #20209: YJIT can leak memory by retaining objects with singleton class https://bugs.ruby-lang.org/issues/20209#change-107354 * Author: alanwu (Alan Wu) * Status: Closed * Backport: 3.0: DONTNEED, 3.1: DONTNEED, 3.2: DONTNEED, 3.3: DONE ---------------------------------------- We've received [reports](https://github.com/ruby/ruby/pull/9693) of YJIT causing memory leaks in production Rails apps by keeping objects that have singleton classes alive. The symptom is similar to #19436. We have found a workaround with https://github.com/ruby/ruby/pull/9693 and would like to have it in the next 3.3 point release. -- https://bugs.ruby-lang.org/ ______________________________________________ ruby-core mailing list -- ruby-core@ml.ruby-lang.org To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/