Community
Participate
Working Groups
Created attachment 260242 [details] log file Version: Neon (4.6) Build id: I20160301-1230 Eclipse Git Team Provider 4.1.2.201511141014 org.eclipse.egit.feature.group Eclipse EGit Java implementation of Git 4.1.2.201511140022 org.eclipse.jgit.feature.group Eclipse JGit I amended a commit and clicked on 'Commit' button in Git Staging view. Then, double clicked on the changed file in History view and started getting OutOfMemory exceptions. After that Eclipse froze and had to be killed to restart. See attached log file.
Probably you could improve memory consumption by *not* using Team->Git->Virtual memory mapping option, if it is set. Otherwise can you please give a repo/commit id in question for reproducing it? How many memory your Eclipse had - default 1024MB or more/less?
(In reply to Andrey Loskutov from comment #1) > Probably you could improve memory consumption by *not* using > Team->Git->Virtual memory mapping option, if it is set. It is not set. > Otherwise can you > please give a repo/commit id in question for reproducing it? https://git.eclipse.org/r/#/c/68145/ I amended CompilationUnitEditor.java from patch set 2. After restarting Eclipse and double clicking the file in History view, I can't reproduce it. > How many memory > your Eclipse had - default 1024MB or more/less? It is default - 1024m.
- what is the result of $ git count-objects -v - what is the size of the jgit object cache (Preferences > Team > Git > Window Cache > Window cache limit) ? next time if you hit this please create a heap dump and analyze it using the Eclipse Memory Analyzer, then we have a chance to identify what may have caused the problem
