It is confirmed that after a connections gets closed, the underlying resources are not properly freed and therefore the WebAssembly runtime/module/instance continue to exist and therefore holding all the memory allocated.
Original post
By running the listener example, I keep seeing growing Alloc and Sys. Waiting between handling incoming connections will not help reducing the memory allocation.
It is confirmed that after a connections gets closed, the underlying resources are not properly freed and therefore the WebAssembly runtime/module/instance continue to exist and therefore holding all the memory allocated.
Original post
By running the listener example, I keep seeing growing
AllocandSys. Waiting between handling incoming connections will not help reducing the memory allocation.