Skip to content

use malloc/free instead of stackAlloc in setMemory (cleaned up) #5646

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 10, 2023

Conversation

mnater
Copy link
Contributor

@mnater mnater commented Apr 7, 2023

cleaned PR. Original: #5625

fixes #5595

Copy link
Member

@kripken kripken left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@kripken kripken enabled auto-merge (squash) April 10, 2023 16:10
@kripken kripken merged commit bd91d8d into WebAssembly:main Apr 10, 2023
radekdoulik pushed a commit to dotnet/binaryen that referenced this pull request Jul 12, 2024
…ssembly#5646)

Memory data segments can be of large size, and might not fit in the stack.

fixes WebAssembly#5595
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

setMemory fails for large data after update to v112
2 participants