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

A javascript error occurred in the main process #56780

Open
cwl9943 opened this issue Jan 27, 2025 · 1 comment
Open

A javascript error occurred in the main process #56780

cwl9943 opened this issue Jan 27, 2025 · 1 comment

Comments

@cwl9943
Copy link

cwl9943 commented Jan 27, 2025

Version

v23.6.1

Platform


Subsystem

No response

What steps will reproduce the bug?

A javascript error occurred in the main process

uncaught exception: 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)

Related to: #49758

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

N/A

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

N/A

What do you see instead?

A javascript error occurred in the main process

uncaught exception: 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)

Related to: #49758

Additional information

No response

@pacexy
Copy link
Contributor

pacexy commented Jan 27, 2025

Please provide more information, at least the steps to reproduce the bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants