-
-
Notifications
You must be signed in to change notification settings - Fork 385
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
diff has memory leak #625
Comments
Same Issue when using libgit 0.24.1 instead of 0.24.0 or when running it on linux (32bit). |
How are you performing the diff? How are you throwing away the result? Are you deleting it or letting the garbage collector decide when to delete it? Do you have some code that shows the issue? |
I extracted the bug as a small script into the following Gist: https://gist.github.com/mrh1997/9925bbb8e5f7b0ab8c88189d562ad42d I recommend to use the attached vagrantfile. Then you may be sure that you are able to reproduce it, as it creates exactly the same machine as I used for testing... Simply run |
@carlosmn: succeeded in repoducing the bug? Or do you need further information? |
probably the same as #943 which was fixed |
running diff on two trees (no matter if Repository.diff(), Tree.diff_to_tree()) seems to have a memory leak.
My testscript walks a big repository from root to head of master and diffs every logentry to its parent.
Although the diff result is thrown away the memory footprint of the process grows and grows (according to the Windows Taskmanager).
At some point I get a MemoryError).
My system is:
The text was updated successfully, but these errors were encountered: