[mypyc] Fix memory leak on property setter call#21095
Open
p-sawicki wants to merge 4 commits intopython:masterfrom
Open
[mypyc] Fix memory leak on property setter call#21095p-sawicki wants to merge 4 commits intopython:masterfrom
p-sawicki wants to merge 4 commits intopython:masterfrom
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
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.
Calling a property setter method results in a memory leak because the setter method internally increfs the passed value and there is no corresponding decref on the caller side. Probably because regular attribute set steals the value so there is no need for a decref there. So add the decref after calling a property setter.
The leak can be observed either by running the updated
testPropertySetterstest that checks for leaks on master or by manually looking at memory use intopwhen running a loop like this one: