Repository navigation
Node v22 hungs when running a specific wasm module #60584
Description
Activity
I suspect you might be looking at the deadlock fixed by #58047 (which was not backported to v22, PR welcomed, I am not sure if I have the bandwith to backport it as I was only nerd-sniped into fixing it to unblock the V8 upgrade).
As a quick workaround, downgrading node from
v22.21.1tov22.16.0(fix #58047 was part of the release note) fixed the issue on my sideNote that I only reproduced the issue on Windows.
On Mac withnode@22.21.1, postinstall runs without hangingReacted by Michael KrieseReacted by Denis BendrikovAs a quick workaround, downgrading node from
v22.21.1tov22.16.0(fix #58047 was part of the release note) fixed the issue on my sideNote that I only reproduced the issue on Windows.
On Mac withnode@22.21.1, postinstall runs without hangingnot really an option for us
- added a commit that references this issue
on Mar 4, 2026 This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.Reacted by Michael Krieseno longer an issue for us as we require node v24
Version
v22.21.1
Platform
Subsystem
No response
What steps will reproduce the bug?
lib.zip
How often does it reproduce? Is there a required condition?
It hungs always, so node never exits and it eats all memory under windows.
What is the expected behavior? Why is that the expected behavior?
the test above should just exit like it does with node v24
What do you see instead?
node never exits
Additional information
see this issue for a longer discussion