ERR_INTERNAL_ASSERTION error

[karakanb]

Version

v18.1.0

Platform

Darwin 6845GLOBAL.local 22.5.0 Darwin Kernel Version 22.5.0: Mon Apr 24 20:52:24 PDT 2023; root:xnu-8796.121.2~5/RELEASE_ARM64_T6000 arm64

Subsystem

No response

What steps will reproduce the bug?

It happened as a popup from Signal app, I am only creating this issue because the popup literally says "create an issue". I have zero clue about why it happens, just sharing in case it is helpful to fix some bugs somewhere.

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

Happened just once after I woke up my computer.

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

There should be no panics like this I guess.

What do you see instead?

Unhandled 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:399:5)
at assert (node:internal/assert:14:11)
at internalConnectMultiple (node:net:1077:3)
at afterConnectMultiple (node:net:1532:5)

Additional information

Feel free to close the issue or point it to a linked issue, just wanted to be a good citizen and report it since the message clearly says "please open an issue".

[paulhh]

I've also been getting this the last couple of days - same message.

Signal 6.20.0
production (Apple silicon)

Ventura 13.4

[targos]

/cc @indutny

[tniessen]

Likely duplicate of #47644.

[spenczar]

I just got this exact error and trace too. Signal v6.20.0, Apple Silicon, Monterey 12.5

[tniessen]

FYI @ShogunPanda. Closing as duplicate of #47644.

[ShogunPanda]

But this is on Node 18. Node 18 has not network family autoselection enabled by default.
@karakanb Can you please confirm you were on Node 20.x?

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

[karakanb]

I have no clue, tbh. I thought I was on v18, that's what I reported, but I don't have access to the same device anymore, therefore I cannot confirm or deny.