ERR_INTERNAL_ASSERTION

[SanderKok01]

Version

v21.1.0

Platform

Microsoft Windows NT 10.0.22621.0 x64

Subsystem

node:internal/assert:14

What steps will reproduce the bug?

I don't know, it sometimes crashes after gathering data from the database. I'm using nodemon with NX.
The command that is running is npm run dev

How often does it reproduce? Is there a required condition?

It happens every once in a while, this is the 5th time in an hour.

What is the expected behavior? Why is that the expected behavior?

No response

What do you see instead?

node:internal/assert:14
    throw new ERR_INTERNAL_ASSERTION(message);
    ^
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)
    at listOnTimeout (node:internal/timers:575:11)
    at process.processTimers (node:internal/timers:514:7) {
  code: 'ERR_INTERNAL_ASSERTION'
}

Additional information

No response

[MrJithil]

Could you please provide a very minimal reproduction steps? A tiny code snippet will be helpful for us to debug the issue.

[SanderKok01]

It is not possible to recreate. The error occurs randomly, when data is being fetched from the DB. This issue appears quite often because fetching happens a lot as well.

[SanderKok01]

Is this issue comparable to #47644 ?
There is not a solution for me in this issue.

[tniessen]

This is most likely due to #44731. cc @ShogunPanda

[ShogunPanda]

@SanderKok01 I'm sorry about the other issue. I'm catching up at work and then I'll finally able to address this.

Even tho is hard for you to reproduce the issue, can you please at least tell us if it happens when connecting to some specific hosts (even local, it doesn't matter) and eventually give us how the connecting host(s) DNS resolve such hosts?

[SanderKok01]

@ShogunPanda The command I'm using is npm run dev, which starts the local development environment at localhost:1337. But after some time, at random, the local server crashes and I have to restart. It always gives off the same error.

The connection to the local server itself is stable. Starting and using goes smoothly, until it just crashes. Sometimes without even doing anything, it just stops.

Please let me know if you have any other questions for me. Happy to help!

[ShogunPanda]

Ok, that makes sense. I'll look into, it. Thanks for your informations.

[tniessen]

I am going to close this as a duplicate of #48763, which is due to #44731.

[ShogunPanda]

This should have been fixed in #51045. Once it gets in 21.x or 20.x please let me know if you have additional problems.