[WIP] Fix memory leak of repository and repo-cached objects #955
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
srajko
force-pushed
the
repo-leak-fix
branch
3 times, most recently
from
225b378
to
f170baa
Compare
This was referenced Mar 18, 2016
srajko
force-pushed
the
repo-leak-fix
branch
7 times, most recently
from
01dc2fe
to
4ec5d58
Compare
Affects: git_blob_owner git_commit_owner git_filter_source_repo git_index_owner git_object_owner git_reference_owner git_remote_owner git_revwalk_repository git_submodule_owner git_tag_owner git_tree_owner
srajko
force-pushed
the
master
branch
2 times, most recently
from
a78275a
to
206d27d
Compare
|
I've completed this in master. |
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.
No description provided.