Community
Participate
Working Groups
I work with Eclipse, EGit and command line git. Frequent branch changes (like 5 checkouts) in command line cause Eclipse to hang.
You might have to up the stack ... with EGit, I run -Xms64m -Xmx1024m or a multi-branch history on a repo will kill eclipse. PW
Can you please provide a thread dump? c.f. http://wiki.eclipse.org/How_to_report_a_deadlock
I do not think providing a deadlock dump will help here - as I have said it is OOME and when there is no more memory Eclipse hangs (and eventually shows error dialog). After a while it starts working a little bit, but generally is unresponsibve, unstable and throws errors very often.
If the application is running out of memory then it's best to ask the VM to create a heap dump when it crashes. Once that has been generated, you can use MAT and analyze the dump to see where most of the memory is being taken up by. If you have the 'History' view up then I'm going to guess it's a bunch of byte[] objects.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
