Fixed existing bug on transaction hashmap#191
Merged
Conversation
JoeCap08055
reviewed
Apr 1, 2024
saraswatpuneet
approved these changes
Apr 1, 2024
Contributor
saraswatpuneet
left a comment
There was a problem hiding this comment.
Lgtm! Joe have a better idea about fixes so consider this as soft approval
JoeCap08055
approved these changes
Apr 2, 2024
1 task
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
3 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.
Goal
The goal of this PR is to address the bug in
transactional-hashmapthat instead of only keeping track of original state it was keeping track of all the intermediate states which was allocating excessive memory and causing Out of memory errors.Closes #190
Discussion
Checklist