Possible memory leak on Chrome when using/abusing bcrypt

[Jopacari]

I am running some performance test on Chrome and I found that when using bcrypt the memory has a huge increase and GC starts consuming CPU trying to save the day. The code can be seen here: https://files.recompute.win/bcrypt_memoryleak.html
The memory jumps to almost 3GB.
The script never finishes as the GC is keep consuming the CPU.
The same script using the slow JS version instead of the wasm version doesn't have this issue.
I am running it using Chrome Version 138.0.7204.169 (Official Build) (64-bit)

[Daninet]

Hey @Jopacari . I think you need to write await fn() instead of fn(). bcrypt returns a promise.

[Jopacari]

You are right. Sorry for bothering with something so trivial.
I have experience with programing but I am new to JS.
Thank you for your quick answer.