Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error [ERR_INTERNAL_ASSERTION] #48278

Closed
hch-2k8 opened this issue Jun 1, 2023 · 6 comments
Closed

Error [ERR_INTERNAL_ASSERTION] #48278

hch-2k8 opened this issue Jun 1, 2023 · 6 comments
Labels
duplicate Issues and PRs that are duplicates of other issues or PRs. net Issues and PRs related to the net subsystem.

Comments

@hch-2k8
Copy link

hch-2k8 commented Jun 1, 2023

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

Stack trace:
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)

Version 6.20.0 (freshly updated)

@mscdex
Copy link
Contributor

mscdex commented Jun 1, 2023

v6.x is no longer supported. For supported versions, please see the information here.

@mscdex mscdex closed this as completed Jun 1, 2023
@climba03003
Copy link
Contributor

I believe the author trying to mention 16.20.0 instead of 6.20.0 since there is no version of 6.20.0.

And the issue is leak of information for any actionable debugging.

@hch-2k8
Copy link
Author

hch-2k8 commented Jun 2, 2023

Nope.

It's a misleading crash information in the product (Signal Desktop v6.20.0) using Node.js on one hand (report it on the Node.js issue tracker [only]), and my "ignorance" on the other hand (Signal version is of no interest for Node.js maintainers.)

However I have no clue which version is used in Signal Desktop neither whether it is indeed related to Node.js itself or to Node use in Signal as the error message also mentions.

@targos
Copy link
Member

targos commented Jun 2, 2023

Let's track the issue in #48281 which is still open.

@tniessen
Copy link
Member

tniessen commented Jun 2, 2023

If this is based on Node.js 20.x, then it's likely a duplicate of #47644.

@tniessen tniessen added duplicate Issues and PRs that are duplicates of other issues or PRs. net Issues and PRs related to the net subsystem. labels Jun 3, 2023
@ShogunPanda
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate Issues and PRs that are duplicates of other issues or PRs. net Issues and PRs related to the net subsystem.
Projects
None yet
Development

No branches or pull requests

6 participants