-
-
Notifications
You must be signed in to change notification settings - Fork 7.4k
Fix ~basic_json causing std::terminate #4654
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
Open
Ignition
wants to merge
1
commit into
nlohmann:develop
Choose a base branch
from
Ignition:fix_4653
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+310
−68
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is still a memory allocation, so you haven't achieved your goal of not allocating memory in the destructor. I take it you are assuming that any failed allocation would result in a thrown allocation that you can catch. Even if that were the case, then you have converted the potential issue from a failed allocation into a stack overflow. It seems to me that the only way to prevent both the stack overflow and the possibility of an allocation failure is the Morris Traversal using the parent pointer. You could simulate that if the parent pointer isn't available using a local container for the current path from the root, but that is also an allocation that can fail.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My goal is not for no allocations. My goal is to avoid std::terminate if an allocator throws. Which can be for more reasons that running out of memory, in my case its because of a quota is exceeded in a subsystem.
I don't want to change the entire representation of an object to make it zero allocations. This is a bigger change than this fix. I just try to 1) reuse existing buffers to flatten where possible, 2) flatten using heap allocation if needed, 3) allow stack call if required.
Its a best effort approach, without restructuring all of the json library. I've had a patch for over a year that works, I'd just like something delivered upstream so I can cleanup downstream project.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My main point is that you are replacing one terminate with another (stack overflow), which the library had previously avoided due to actual users experiencing it. I'm just a contributor but to me that is a non-starter, especially when it's possible to avoid both with the addition of a single pointer, and when that pointer is already there with a configuration option.