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
Rework GitStatusProvider to use cached status storage #10690
Conversation
@@ -1,119 +0,0 @@ | |||
/* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't remove this class for now, just mark as Deprecated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed
collectProjectFiles(rootDirPathProvider.get()); | ||
} | ||
|
||
private void collectProjectFiles(String root) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I propose add @PostConstruct and remove call this method from constructor
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done
ci-test |
ci-test build report: |
What does this PR do?
JGit status command on big projects (Eclipse Che) uses a lot of RAM.
When deep expand to some folder is performed, Git status is called on each folder expand:
This causes a huge leap of RAM and finally OOM appears:
In this PR
GitStatusProvider
is reworked to call Git status only if it is really needed e.g. file was modified. The provider is based on a cached Git Status Map that is updated from Git Events.What issues does this PR fix or reference?
#10696
Release Notes
Fix
java.lang.OutOfMemoryError
on large projects.Docs PR
N/A