We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Thanks for the bug report!
I think there might be a memory leak when creating a module.
When I create a module in an endless loop, the memory usage as is shown by free command on Linux increases endlessly.
Here is the code.
package main import ( "io/ioutil" "runtime" "time" "github.com/wasmerio/wasmer-go/wasmer" ) func main() { wasmBytes, _ := ioutil.ReadFile("./demo.wasm") go func() { for { time.Sleep(time.Second) runtime.GC() } }() for { engine := wasmer.NewEngine() store := wasmer.NewStore(engine) module, _ := wasmer.NewModule(store, wasmBytes) module.Close() store.Close() } }
I expect the memory usage is under a stable number.
Memory usage keeps increasing.
The text was updated successfully, but these errors were encountered:
This is fixed in Wasmer 2.1, but the Go bindings have not yet been updated to use that version.
Sorry, something went wrong.
I'm also hit by this issue. Is there an ETA for updated Go bindings?
Is there something I can do to help?
No branches or pull requests
Thanks for the bug report!
Describe the bug
I think there might be a memory leak when creating a module.
When I create a module in an endless loop, the memory usage as is shown by free command on Linux increases endlessly.
Steps to reproduce
Here is the code.
Expected behavior
I expect the memory usage is under a stable number.
Actual behavior
Memory usage keeps increasing.
The text was updated successfully, but these errors were encountered: