An unknown error [ERR_INTERNAL_ASSERTION]: This is caused by either a bug in Node.js or incorrect usage of Node.js internals.

[teddy1565]

Version

20.9.0

Platform

x86_64 x86_64 x86_64 GNU/Linux

Subsystem

aws 22.04.1-Ubuntu SMP

What steps will reproduce the bug?

i don't know
but i use some node_modues

pm2, mqtt, child_process

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

just once

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

no any error

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 new NodeError (node:internal/errors:406:5)
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'
}

Node.js v20.9.0

Additional information

I'm not sure it's my wrong or not, but at v10.24.1 & v18.12.1 never appeared

[enBonnet]

Same issue here.

[lpinca]

Related to #44731, duplicate of #50436.

[tniessen]

Duplicate of #48763, which is due to #44731. cc @ShogunPanda

[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.

[rodolfoprr]

@ShogunPanda is there any ETA for the fix to get to 20.x? Thanks.

[ShogunPanda]

@rodolfoprr See: #50655 (comment)

[naveenjpr]

MongoDB Compass has encountered an unexpected error
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:406:5)
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)

my node version v20.13.1

[ShogunPanda]

@naveenjpr MongoDB Compass uses Electron, which internally uses a different Node.js version. Can you please tell us the MongoDB version?

[naveenjpr]

mongodb-windows-x86_64-7.0.11-signed (1).msi

[naveenjpr]

@naveenjpr MongoDB Compass uses Electron, which internally uses a different Node.js version. Can you please tell us the MongoDB version?

mongo db version mongodb-windows-x86_64-7.0.11-signed (1).msi

[tniessen]

Looks like the most recent version of MongoDB Compass uses "electron": "^29.4.3", which appears to correspond to Node.js 20.9.0 (at the time of writing).

[ShogunPanda]

So that's the issue. We've fixed this in #51045 which was late incorporated in Node.js 20.12.0.

@naveenjpr Once Compass updates its Electron version you should be good to go.