Bug #20898: Backport https://github.com/ruby/ruby/pull/9737 to Ruby 3.3 and 3.2

• Status: Closed
• Assignee: -
• Target version: -
• Backport: 3.1: UNKNOWN, 3.2: DONE, 3.3: DONE

[katei (Yuta Saito)]

The memory corruption issue on Wasm led to mysterious crashes and consumed much debugging time. It's nice to backport the fix to save developers time.

https://github.com/ruby/ruby/pull/9737

[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-field. (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.

[k0kubun (Takashi Kokubun)]

• Backport changed from 3.1: UNKNOWN, 3.2: DONE, 3.3: DONE to 3.1: UNKNOWN, 3.2: REQUIRED, 3.3: DONE

[nagachika (Tomoyuki Chikanaga)]

• Backport changed from 3.1: UNKNOWN, 3.2: REQUIRED, 3.3: DONE to 3.1: UNKNOWN, 3.2: DONE, 3.3: DONE

ruby_3_2 1fc0895971812d5287b23d8cbb00529e425041c0 merged revision(s) 0d4de0f4b1b9ac90be437bf1bac6851dd1d96fd0.