Session runs leak memory #86
Merged
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
|
Great catch! We'd like to set up an automated valgrind test to catch this stuff (#69), but it's a bit difficult. |
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.
Memory leaks during repeated session runs. I noticed that the
runmethod creates wrapping tensors of the input. However, the caller retains ownership ofTF_Tensors passed toTF_Runsince Tensorflow 0.12.0:https://github.com/tensorflow/tensorflow/blob/master/RELEASE.md#breaking-changes-to-the-api-2
Passing the input tensor vector from the step resolves this leak.