-
-
Notifications
You must be signed in to change notification settings - Fork 11.1k
BUG: fix datetime/timedelta hash memory leak #29411
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
Conversation
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 noticed some preexisting issues with error handling and suggested a fix.
Also ping @walshb - FYI there were some error checking and reference counting bugs that were missed in the datetime/timedelta hash PR we merged last year.
Co-authored-by: Nathan Goldbaum <nathan.goldbaum@gmail.com>
Co-authored-by: Nathan Goldbaum <nathan.goldbaum@gmail.com>
Seems to be in order. |
Thanks for closing the loop on this @kostayScr. This will be backported to the 2.3 release branch and will be included in NumPy 2.3.2. |
* BUG: fix datetime/timedelta hash memory leak * get metadata directly from scalar object Co-authored-by: Nathan Goldbaum <nathan.goldbaum@gmail.com> * BUG: remove unnecessary Py_DECREF Co-authored-by: Nathan Goldbaum <nathan.goldbaum@gmail.com> * BUG: remove dtype variable declaration that is not used anymore --------- Co-authored-by: Nathan Goldbaum <nathan.goldbaum@gmail.com>
BUG: fix datetime/timedelta hash memory leak (#29411)
Fixes lack of a Py_DECREF() call in the datetime/timdelta hash function. Closes #29397.