# SWI Prolog WASM Memory issue resolved

**URL:** <https://swi-prolog.discourse.group/t/swi-prolog-wasm-memory-issue-resolved/6509>\
**Category:** General\
**Created:** [April 30, 2023, 1:58pm UTC](https://swi-prolog.discourse.group/t/swi-prolog-wasm-memory-issue-resolved/6509 "2023-04-30T13:58:39Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jeswr](https://yyz2.discourse-cdn.com/free1/user_avatar/swi-prolog.discourse.group/jeswr/32/5469_2.png) [@jeswr](https://swi-prolog.discourse.group/u/jeswr)\
**Post date:** [April 30, 2023, 1:58pm UTC](https://swi-prolog.discourse.group/t/swi-prolog-wasm-memory-issue-resolved/6509/1 "2023-04-30T13:58:39Z")

</div>

As of [Release v3.2.2 · SWI-Prolog/npm-swipl-wasm · GitHub](https://github.com/SWI-Prolog/npm-swipl-wasm/releases/tag/v3.2.2) the swipl-wasm npm package no longer has the memory leakage issues described in [this thread](https://swi-prolog.discourse.group/t/firebase-functions-swi-prolog-wasm-node-memory-build-up-issue/6435).

I tried to write this as a reply in the thread but am allowed no more than 3 replies.

cc @atava @rla