Repository navigation
ERR_INTERNAL_ASSERTION #51285
Description
Version
v20.10.0
Platform
windows
Subsystem
No response
What steps will reproduce the bug?
At this moment, it happens in a complex app and even while debugger was attached, so hard to provide any reproduceable snippet. I haven't used any special internal functionality or overrides. what the app did, was that it created a loop of around 20 promises, and waited to finish all of them. only few were resolved, while the error popped up
How often does it reproduce? Is there a required condition?
very rarely, i have been using the app quite long and it's the first time I saw this issue
What is the expected behavior? Why is that the expected behavior?
No response
What do you see instead?
Error [ERR_INTERNAL_ASSERTION]: This is caused by either a bug in Node.js or incorrect usage of Node.js internals.
Please open an issue with this stack trace at https://github.com/nodejs/node/issues
at assert (node:internal/assert:14:11)
at internalConnectMultiple (node:net:1118:3)
at Timeout.internalConnectMultipleTimeout (node:net:1687:3)Additional information
No response
Activity
tniessen commentedon Dec 25, 2023
This should hopefully finally be fixed by #51045.
dzlandis commentedon Dec 26, 2023
Just got this same error, thanks for posting. Waiting for the release update with the fix 🙏
sushxnt commentedon Dec 26, 2023
Thanks for release update!
ductridev commentedon Dec 28, 2023
Just got this same error. Hope the new version will be released asap :)
IvanIvannov1952 commentedon Dec 28, 2023
I my case, similar error I can see when I execute
npm run test, and every execution return different number of failed testsI hope the release will be very soon
aduh95 commentedon Jan 8, 2024
The fix has been released with 21.6.0, any chance you could confirm if the issue is gone using this version?
ttodua commentedon Jan 10, 2024
thabks for folllw up.
if i face it again, i'll inform you
adarshmadrecha commentedon Jan 21, 2024
We migrated our 6 webservers to node v21.6.0 and confirm that this issue is no longer faced.
devopsmash commentedon Jan 21, 2024
Can someone confirm that this has been fixed in 20.11.0 as well?
aduh95 commentedon Jan 21, 2024
Thanks for the confirmation! The fix should be in the Node.js 20.12.0 (or 20.13.0 is 20.12.0 is a security release).
Closing this issue, #51354 tracks the same problem and will stay open until the fix is backported to the 20.x release line.
VinathPK commentedon Mar 11, 2025
i am using v22,14.0 and I am getting this issue. Any clue on how to fix it?