Issue #20898 has been updated by k0kubun (Takashi Kokubun). Status changed from Open to Closed Backport changed from 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN to 3.1: UNKNOWN, 3.2: DONE, 3.3: DONE To request a backport (of a commit merged to master), you need to "close" the ticket and specify REQUIRED in the Backport field https://github.com/ruby/ruby/wiki/How-To-Request-Backport#backport-custom-fi.... (I already did so for this ticket) Also, please consider filing a pull request to the corresponding branches (`ruby_3_3` and `ruby_3_2`) on GitHub. Backporting patches often causes a conflict, and we end up requesting the original patch author to file a pull request to resolve it anyway. ---------------------------------------- Bug #20898: Backport https://github.com/ruby/ruby/pull/9737 to Ruby 3.3 and 3.2 https://bugs.ruby-lang.org/issues/20898#change-110666 * Author: katei (Yuta Saito) * Status: Closed * Backport: 3.1: UNKNOWN, 3.2: DONE, 3.3: DONE ---------------------------------------- The memory corruption issue on Wasm led to mysterious crashes and [consumed much debugging time](https://github.com/ruby/ruby.wasm/issues/555). It's nice to backport the fix to save developers time. https://github.com/ruby/ruby/pull/9737 -- https://bugs.ruby-lang.org/