Skip to content
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

Move some scopes around to fix a leak on raising a trap #2803

Merged
merged 1 commit into from
Apr 5, 2021

Conversation

alexcrichton
Copy link
Member

Some recent refactorings accidentally had a local Store on the stack
when a longjmp was initiated, bypassing its destructor and causing
Store to leak.

Closes #2802

Some recent refactorings accidentally had a local `Store` on the stack
when a longjmp was initiated, bypassing its destructor and causing
`Store` to leak.

Closes bytecodealliance#2802
@github-actions github-actions bot added the wasmtime:api Related to the API of the `wasmtime` crate itself label Apr 5, 2021
@github-actions
Copy link

github-actions bot commented Apr 5, 2021

Subscribe to Label Action

cc @peterhuene

This issue or pull request has been labeled: "wasmtime:api"

Thus the following users have been cc'd because of the following labels:

  • peterhuene: wasmtime:api

To subscribe or unsubscribe from this label, edit the .github/subscribe-to-label.json configuration file.

Learn more.

@alexcrichton alexcrichton merged commit 04bf6e5 into bytecodealliance:main Apr 5, 2021
@alexcrichton alexcrichton deleted the fix-leak branch April 5, 2021 15:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wasmtime:api Related to the API of the `wasmtime` crate itself
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Trap in host function leaks memory, 0.25 regression
2 participants