Repository navigation
Error [ERR_INTERNAL_ASSERTION]: This is caused by either a bug in Node.js or incorrect usage of Node.js internals. #56323
Description
Version
v18.15.0
Platform
Linux dev 5.14.0-542.el9.x86_64 #1 SMP PREEMPT_DYNAMIC Wed Dec 11 17:15:50 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
Subsystem
No response
What steps will reproduce the bug?
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 new NodeError (node:internal/errors:399:5)
at assert (node:internal/assert:14:11)
at internalConnectMultiple (node:net:1077:3)
at Timeout.internalConnectMultipleTimeout (node:net:1565:3)
at listOnTimeout (node:internal/timers:571:11)
at process.processTimers (node:internal/timers:512:7) {
code: 'ERR_INTERNAL_ASSERTION'
} uncaughtException
How often does it reproduce? Is there a required condition?
Almost every time the server starts.
What is the expected behavior? Why is that the expected behavior?
Expected behaviour is for the server to start without any errors.
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 new NodeError (node:internal/errors:399:5)
at assert (node:internal/assert:14:11)
at internalConnectMultiple (node:net:1077:3)
at Timeout.internalConnectMultipleTimeout (node:net:1565:3)
at listOnTimeout (node:internal/timers:571:11)
at process.processTimers (node:internal/timers:512:7) {
code: 'ERR_INTERNAL_ASSERTION'
} uncaughtException
Additional information
No response
Activity
aduh95 commentedon Dec 20, 2024
Bug was fixed on Node.js 20.12+, it looks like that error is coming from an Electron app, you should report that to them instead, asking them to update the version of Node.js they're using.
ERR_INTERNAL_ASSERTIONwith Strapi CLI #51354