-
-
Notifications
You must be signed in to change notification settings - Fork 18.9k
BUG: fix memory leak in JSON datetime serialization #62217
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
Merged
Merged
Changes from 2 commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
791bb41
fix: memory leak in JSON datetime serialization
Alvaro-Kothe f7b2f5b
fix: flag to free `cStr` in `Object_getBigNumStringValue`
Alvaro-Kothe f324bd8
fix: use dynamic allocated memory to store strings
Alvaro-Kothe 15c19c0
fix: replace PyObject_Malloc with PyMem_Malloc
Alvaro-Kothe 1ea0283
fix: drop `const` qualifier in `cStr`
Alvaro-Kothe 0925e6b
fix: remove void pointer case in PyMem_Free
Alvaro-Kothe 62b0e26
fix: create const for default `cStr` size
Alvaro-Kothe 0f20b7d
try to fix ci error
Alvaro-Kothe 05f4926
hack: go back to use `PyObject_*` because of CI errors
Alvaro-Kothe 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
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.
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.
Generally the problem with the JSON code is that over time we have incrementally added many different state management operations, and it is not always clear how they should work in tandem. So I am a little hesitant to add more state to solve the current issue. Is it possible to solve the issue without changing this struct?
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.
Any suggestions on how to do that? Revert the changes in fb6c4e3 that make some of the uses of
cStr
stack allocated? It doesn't seem possible to make all uses ofcStr
stack allocated, at least at first glance.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.
Sure that might be a reasonable approach
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.
I removed the
freeCStr
flag and stored all the strings assigned in*IterNext
in dynamic memory.