-
Notifications
You must be signed in to change notification settings - Fork 29.9k
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
"cipher.final()" results in an abort #38035
Comments
The crash traces look the same as #37922 |
Duplicate of #38015. Although it's a different method, it's clearly the same underlying bug, or at least it must be related. |
Actually, The failed assertion is located here: node/src/crypto/crypto_cipher.cc Lines 847 to 849 in 640fe94
|
Hi, I just spent some hours to find a bug in my program. Before filing the bug report I searched for similar and came to this here. Additional Information:
Thank you very much ! |
@Ayase-252 : // a) Buffer's hex converter works: // b) crypto's hex-converter fails: So, if you are there changing and afterwards testing the code anyway, maybe you could consider whether to add the trim() like Buffer.from() does? The nastyness of the whitespace was, that You cannot easily see it in the textfile where the '\r\n' comes from :-) For completenes, here is my abort message. |
What steps will reproduce the bug?
Setup a node instance,
and run the following javascript code.
Then the node instance occurs an abort.
How often does it reproduce? Is there a required condition?
This abort can always be triggered following the steps above.
What is the expected behavior?
If any error occurs, an exception or other similar error-reporting stuff should be thrown. There is no reason to abort the whole node process.
What do you see instead?
Additional information
The text was updated successfully, but these errors were encountered: