Hi there! I love ffmpeg.wasm! Thank you for the nice library!!

I am wondering which or not this behavior is a bug, so I post this in GitHub Discussion.

I developed the system, in that system the application record user’s screen and process it with ffmpeg wasm in browser. While I was developing this, I noticed that ffmpeg.wasm run command failed with high-resolution video input with memory access out of bounds error. (maybe 1024px is threshold)

I am not familiar with Wasm in the browser, but I infer that allocated memory is not enough in the data exchange in js -> wasm.

Is there any workaround or solution?