Fix OOM when parsing bare hexadecimal literal.#229
Merged
jordanbtucker merged 2 commits intojson5:masterfrom Apr 4, 2020
mkantor:bare-hexadecimal
Merged
Fix OOM when parsing bare hexadecimal literal.#229jordanbtucker merged 2 commits intojson5:masterfrom mkantor:bare-hexadecimal
jordanbtucker merged 2 commits intojson5:masterfrom
mkantor:bare-hexadecimal
Conversation
Member
|
Thanks for finding and fixing this bug. The fix should be live in v2.1.3 now. |
This was referenced Feb 17, 2023
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When parsing a bare hexadecimal number like
JSON5.parse('0x1'), the parser was looping forever here because it was reading to the end andutil.isHexDigit(undefined) === true.I updated all of the
util.is*functions to returnfalseforundefinedand added some regression tests.Fixes #228.