Possible memory leak in decode function?

[dnish]

Hey,
we are using a library which depends on version 0.1.5. We noticed a heavy memory increase in our application and started debugging it via node profiler. After getting some snapshots, we noticed a big JSArrayBufferData object which contains a call to the decode function of the @cwasm/webp package. The object never gets collected by garbage collector, even when we force a cleaning via global.gc().

[LinusU]

Hey!

I think that this is because there is no way to shrink the WASM instance allocated memory once it requests more. I'm sure that there was another thread about this one another cwasm package but I cannot seem to find it now 🤔

It this is the same issue, you should see a constant memory usage around the encoded + decoded size of the largest image ever decoded. But it shouldn't grow unbounded. Is this what you are experiencing?

I'm very open to solutions to this, but I'm not sure that there is something straight forward. Potentially we could schedule a job to with something like setTimeout to tear down and create a new WASM instance if there hasn't been any decode calls in a while 🤔

[LinusU]

Seems like there is some upstream work that could enable us to shrink the memory after each encoding 🙌

WebAssembly/memory-control#6