Backport WASI setjmp handler memory leak fixes to Ruby 3.2#14790
Closed
white-axe wants to merge 1 commit intoruby:ruby_3_2from
Closed
Backport WASI setjmp handler memory leak fixes to Ruby 3.2#14790white-axe wants to merge 1 commit intoruby:ruby_3_2from
white-axe wants to merge 1 commit intoruby:ruby_3_2from
Conversation
Member
|
This seems to not security issue and build failure. I don't want to backport normal bugfix to 3.2. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request backports the following three pull requests to Ruby 3.2 as described at https://bugs.ruby-lang.org/issues/21626.
I ran the ruby.wasm tests on this pull request at https://github.com/white-axe/ruby.wasm/actions/runs/18362097645/job/52310197156.