Skip to content

Closing file handles/streams #176

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 25, 2014

Conversation

craigez
Copy link
Contributor

@craigez craigez commented Jul 25, 2014

Our debugging of GitPython during usage a while ago showed we were leaking some file handles. We think this resolves some of the issues.

@Byron
Copy link
Member

Byron commented Jul 25, 2014

Thanks a lot for this contribution - plenty of issues showed up in the past because of this !

Byron added a commit that referenced this pull request Jul 25, 2014
@Byron Byron merged commit 22a2103 into gitpython-developers:master Jul 25, 2014
@craigez
Copy link
Contributor Author

craigez commented Jul 25, 2014

There are sill more somewhere but we haven't found them yet.

@Byron
Copy link
Member

Byron commented Jul 25, 2014

Gitdb is the other location which deals with files, sometimes indirectly through the use of smmap. I would suspect smmap, as each mmap opened on a file will effectively duplicate the file-handle. If the original is not closed, there would be a leak. It's just a guess of mine, which would need to be verified.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants