Memory issue (PluginError: WebAssembly.instantiate(): Out of memory: wasm memory)

[pekeq]

Out of memory error occur like following:

(node:45565) UnhandledPromiseRejectionWarning: RangeError: WebAssembly.instantiate(): Out of memory: wasm memory
(Use `node --trace-warnings ...` to show where the warning was created)
(node:45565) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:45565) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:45565) UnhandledPromiseRejectionWarning: RangeError: WebAssembly.instantiate(): Out of memory: wasm memory
(Use `node --trace-warnings ...` to show where the warning was created)
(node:45565) UnhandledPromiseRejectionWarning: RangeError: WebAssembly.instantiate(): Out of memory: wasm memory
(Use `node --trace-warnings ...` to show where the warning was created)
failed to asynchronously prepare wasm: RangeError: WebAssembly.instantiate(): Out of memory: wasm memory
RangeError: WebAssembly.instantiate(): Out of memory: wasm memory

• Error raised when running pipe(squoosh()) multiple times.
• This is known issue. (Node.js - abort(RangeError: WebAssembly.instantiate(): Out of memory: wasm memory) GoogleChromeLabs/squoosh#1065)
• Some workarounds exist.
  • Don't create multiple ImagePool instance. Create singleton instance.
  • Apply patch to ensure to free wasm memory. (Fix memory leak in image optimization vercel/next.js#23565)
  • Rollback libsquoosh to previous version.

[pekeq]

Changed the implementation to use a single pool.
Testing has not shown any problems, so I'll close this issue.
If the problem occurs again, open another case.