Explicitly trigger GC prior to counting; fixes #39. #40
Conversation
This file contains 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
mitsuhiko
added a commit
that referenced
this pull request
Jan 13, 2016
Explicitly trigger GC prior to counting; fixes #39.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Thanks to a touch of assistance from #pypy, an explicit call to
gc.collect()will force the objects to be collected rather than letting the runtime defer cleanup to some indeterminate future time.Huge warning: This is not guaranteed to continue working in future pypy versions. Attempting to manipulate the GC is generally an Unwise Thing to Do™, Not Portable Between Runtimes™, and not too dissimilar to direct manipulation of the GIL. It'll probably be fine, but pypy supports modular GC policies and this has only been tested under the default policy.