-
Notifications
You must be signed in to change notification settings - Fork 824
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
[C API] Memory leak #3438
Comments
I think this has been fixed now, on master, with latest Instance memory leak. Can you check again and see if you still see memory leak? |
It's still reproducible on both master branch and v3.1.1. |
oh, ok. So it's another leak. Thanks for the testing, I'll investigate on this later. |
hello! @ptitSeb I would like to mention that I've posted this issue wasmerio/wasmer-go#393 on |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Feel free to reopen the issue if it has been closed by mistake. |
Describe the bug
When whole
wasmer
related cleanup calls are done, not whole memory is released. This scenario can be also observed on slightly modified example files contained in this repository. Details described below. Is this known/expected behavior?Steps to reproduce
lib/c-api/examples
.main
function into infinitewhile
loop for example files likewasi.c
orimports-exports.c
orexports-function.c
.top
.Expected behavior
Memory usage should not keep growing continuously (there is cleanup logic at the end of main/loop - are these all required calls?).
Actual behavior
Memory keeps growing.
Additional context
The text was updated successfully, but these errors were encountered: