-
Notifications
You must be signed in to change notification settings - Fork 30.7k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
crypto.checkPrime results in an abort #56512
Comments
santigimeno
added a commit
to santigimeno/node
that referenced
this issue
Jan 11, 2025
santigimeno
added a commit
to santigimeno/node
that referenced
this issue
Jan 11, 2025
santigimeno
added a commit
to santigimeno/node
that referenced
this issue
Jan 13, 2025
Ceres6
pushed a commit
to Ceres6/node
that referenced
this issue
Jan 13, 2025
Fixes: nodejs#56512 PR-URL: nodejs#56559 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Version
v22.11.0
Platform
Subsystem
crypto
What steps will reproduce the bug?
Setup a node instance,
and run the following javascript code.
Then the node instance aborts after a few seconds.
How often does it reproduce? Is there a required condition?
This issue can always be triggered by following the steps above.
What is the expected behavior? Why is that the expected behavior?
If any error occurs, an exception or similar error-reporting stuff should be thrown, caught, and handled correctly. There is no reason to abort the whole node process.
What do you see instead?
Additional information
No response
The text was updated successfully, but these errors were encountered: