Wasmtime GitHub notifications bot (May 05 2022 at 14:50): Wasmtime GitHub notifications bot (May 05 2022 at 14:50):YannikSc labeled issue #4099:
Note: I'm not sure if my implementation is correct, so please correct me if my implementation or expectations are wrong.
Test Case
Example project is available here
Steps to Reproduce
- Create a wasmtime project with wasi support (wasmtime_wasi)
- Build the
WasiCtxwithinherit_env- Run a function a couple times
- Leak memory
Expected Results
It might be a user issue, as I'm not sure if my implementation is correct, but I would assume, that it is.
So in this case my expectation would be, that the memory at the end is likely the same as the one at the start.
Actual Results
The memory size at the end is (for 2000 function calls in my example) ~10 time bigger than at the beginning
Versions and Environment
Wasmtime & Wasmtime_wasi version: 0.36.0
uname -srm: Linux 5.17.5-zen1-1-zen x86_64
Wasmtime GitHub notifications bot (May 05 2022 at 14:50):YannikSc opened issue #4099:
Note: I'm not sure if my implementation is correct, so please correct me if my implementation or expectations are wrong.
Test Case
Example project is available here
Steps to Reproduce
- Create a wasmtime project with wasi support (wasmtime_wasi)
- Build the
WasiCtxwithinherit_env- Run a function a couple times
- Leak memory
Expected Results
It might be a user issue, as I'm not sure if my implementation is correct, but I would assume, that it is.
So in this case my expectation would be, that the memory at the end is likely the same as the one at the start.
Actual Results
The memory size at the end is (for 2000 function calls in my example) ~10 time bigger than at the beginning
Versions and Environment
Wasmtime & Wasmtime_wasi version: 0.36.0
uname -srm: Linux 5.17.5-zen1-1-zen x86_64
Wasmtime GitHub notifications bot (May 05 2022 at 15:00):YannikSc edited issue #4099:
Note: I'm not sure if my implementation is correct, so please correct me if my implementation or expectations are wrong.
Test Case
Example project is available here
Steps to Reproduce
- Create a wasmtime project with wasi support (wasmtime_wasi)
- Build the
WasiCtxwithinherit_env- Run a function a couple times
- Leak memory
Expected Results
It might be a user issue, as I'm not sure if my implementation is correct, but I would assume, that it is.
So in this case my expectation would be, that the memory at the end is likely the same as the one at the start.
Actual Results
The memory size at the end is (for 2000 function calls in my example) ~10 time bigger than at the beginning
Versions and Environment
Wasmtime & Wasmtime_wasi version: 0.36.0
uname -srm: Linux 5.17.5-zen1-1-zen x86_64edit: This also happens if the
envmethod is used
Last updated: Nov 22 2024 at 17:03 UTC