Avoid retaining evaluate out arrays#560
Open
gaoflow wants to merge 1 commit into
Open
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
1 participant
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.
Fixes #558.
validate()cached theout=array directly in_numexpr_lastsore_evaluate()could reuse it. That kept the most recent output array alive even after the caller deleted their last reference.This stores a weak reference for cached
out=instead.re_evaluate()resolves it when called, so live output arrays are still reused, but released arrays are no longer pinned by the cache.Tests:
.venv/bin/python -m pytest numexpr/tests/test_numexpr.py -q.venv/bin/python -m pytest --pyargs numexpr -q.venv/bin/python -m compileall -q numexpr