-
Notifications
You must be signed in to change notification settings - Fork 30k
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
libc++abi: terminating due to uncaught exception of type std::out_of_range: basic_string Abort trap: 6 #47889
Labels
confirmed-bug
Issues with confirmed bugs.
url
Issues and PRs related to the legacy built-in url module.
Comments
/cc @nodejs/url |
I think this is the issue of Ada 2.0 |
Reasonable. |
Yes. It is from ada. |
@anonrig Please review the potential fix. |
|
@himself65 Yes. We definitively had a bug in ada. I think @anonrig will push a fix. |
Released Ada v2.3.1 with the fix to this issue thanks to @lemire |
Thank you all for fixing this issue. 👏 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
confirmed-bug
Issues with confirmed bugs.
url
Issues and PRs related to the legacy built-in url module.
Version
v20.0.0
Platform
Darwin Flora.local 22.5.0 Darwin Kernel Version 22.5.0: Tue Apr 25 04:06:50 PDT 2023; root:xnu-8796.121.2~8/RELEASE_ARM64_T6020 arm64
Subsystem
URL
What steps will reproduce the bug?
When creating a URL object with some invalid url strings, it's straightforward to reproduce:
libc++abi: terminating due to uncaught exception of type std::out_of_range: basic_string Abort trap: 6
It was initially found in this use case: mozilla/readability#801
How often does it reproduce? Is there a required condition?
It can be reproduced every time on Linux and macOS as well.
What is the expected behavior? Why is that the expected behavior?
It should throw an error just like other invalid URLs.
What do you see instead?
libc++abi: terminating due to uncaught exception of type std::out_of_range: basic_string Abort trap: 6
Additional information
N/A
The text was updated successfully, but these errors were encountered: