Skip to content

ERR_INTERNAL_ASSERTION #50754

Closed as not planned
Closed as not planned
@SanderKok01

Description

@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

Metadata

Metadata

Assignees

No one assigned

    Labels

    confirmed-bugIssues with confirmed bugs.duplicateIssues and PRs that are duplicates of other issues or PRs.netIssues and PRs related to the net subsystem.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions