Allocations occurred in the helper library tinygo/v0 has introduced risk of memory leak. While Go is a garbage-collected language, memory leak may only happen when we compile with tinygo and use -gc=leaking.
Although -gc=leaking is somewhat helpful at further reducing the size of a compiled artifact, it is important to note that anything failing the compilation with -gc=none (i.e., allocates on-heap memory) will subject to memory leak if compiled using -gc=leaking.
In this case, we should probably consider compiling current example WATMs with -gc=conservative (or -gc=precise).
Allocations occurred in the helper library
tinygo/v0
has introduced risk of memory leak. While Go is a garbage-collected language, memory leak may only happen when we compile withtinygo
and use-gc=leaking
.Although
-gc=leaking
is somewhat helpful at further reducing the size of a compiled artifact, it is important to note that anything failing the compilation with-gc=none
(i.e., allocates on-heap memory) will subject to memory leak if compiled using-gc=leaking
.In this case, we should probably consider compiling current example WATMs with
-gc=conservative
(or-gc=precise
).