Skip to content

wasmvm suffers from memory corruption and memory leaks #631

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

Open
faddat opened this issue Mar 22, 2025 · 2 comments
Open

wasmvm suffers from memory corruption and memory leaks #631

faddat opened this issue Mar 22, 2025 · 2 comments

Comments

@faddat
Copy link
Contributor

faddat commented Mar 22, 2025

This was reported privately but there's been no communication in a month or more, so I a reporting it publicly

@pinosu
Copy link
Collaborator

pinosu commented Mar 27, 2025

Hi @faddat, thanks for your contribution.
I copied all of your tests from PR #596 and fixed them, as they were failing due to some setup issues. In this PR #633 , I intentionally left out your changes to non-test files to avoid introducing new bugs.

All tests are now passing—you can review them in the linked PR. The only tests I did not copy are those in memorycorruption_test.go, which fail because the uploaded .wasm files are not valid contracts.

@faddat
Copy link
Contributor Author

faddat commented Apr 17, 2025

THANK YOU!

<3

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

No branches or pull requests

2 participants