-
-
Notifications
You must be signed in to change notification settings - Fork 10.9k
BUG: Fix memory leak in array-coercion error paths #17421
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
Conversation
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
Also uses PyMem_*, since those seem the more approriate functions.
Hmm, unexpected core dump. |
Yeah, in the FFT tests? Pasting it here, and restarting the test since it seems a bit confusing (albeit, maybe not impossible).
|
Eh, travis CI isn't showing me the rerun button on this PR? Just going for close+reopen... |
Thanks Sebastian. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Simple enough fix,
PyMem_*
is the right thing to begin with, I think. Repeating was necessary for me to see this with valgrind due to the cache, I am not sure why I didn't see it with pytest-leaks (I thought thePyMem_
allocated memory blocks should be noticed lost, but...The second path may not be covered by a test, but I expect it is somewhere, lets see what codecov thinks.