-
Notifications
You must be signed in to change notification settings - Fork 324
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
Running out of memory, catching the OSError exception #187
Comments
@AUTplayed Gitinspector itself doesn't really require that much memory... All it does is keep a hashmap of authors/insertions+deletions and some other information... However, when running, it does starts multiple git instances. Gitinspector will start as many git instances as there are cpu threads in the system. As you can see from the exception, this is also where things fail. So if you are running out of memory, you could try decreasing NUM_THREADS in blame.py and changes.py. It will slow things down siginifcantly, but also keep memory usage down. It might actually be a good idea to catch this exception and make the thread wait a bit. Maybe we could dynamically decrease NUM_THREADS when running out of memory. Setting this for the 0.5.0 milestone. |
when will publish the 0.5.0 version? |
@370672701 When I have time to sit down with gitinspector. There is no estimated release date at the moment. |
Hi, when I try to inspect a very large repository I'm getting these errors:
Checking my memory usage results in 8GB/8GB used.
You probably won't be able to do anything against this, but just wanted to let you know..
The text was updated successfully, but these errors were encountered: