Community
Participate
Working Groups
Build Identifier: M20100909-0800 I tried to install egit/jgit and eclipse said it needs to restart. I confirmed and it proceeded until the splash screen, were it hung, chewing all cpu it could get. After ten minutes or so I got a stack trace using jpid and jstack and killed eclipse. Reproducible: Didn't try
Created attachment 185742 [details] the stack trace
This isn't a EGit/JGit issue... something else is causing Eclipse to crash...
The deadlock happened during the restart caused by the EGit/JGitinstall process, that's pretty much all I know. The root might well be something else.
1) Note that stack trace indicates that "OpenJDK" VM was used. That is not a reference VM that we test against. See also bug 326721. 2) It does not look like a deadlock for me. The stack trace indicates that the main thread is waiting for the Shell.setVisible() request to be processed by the OS. The stack trace looks somewhat unusual in that the same object is reported locked by two different threads: "Thread-3" prio=10 tid=0x000000000194d800 nid=0x2a18 in Object.wait() java.lang.Thread.State: WAITING (on object monitor) - waiting on <0x00007f515e324698> - locked <0x00007f515e324698> "Thread-2" prio=10 tid=0x0000000001104000 nid=0x2a17 in Object.wait() java.lang.Thread.State: WAITING (on object monitor) - waiting on <0x00007f515dc6f408> - locked <0x00007f515dc6f408> "main" prio=10 tid=0x0000000000d29000 nid=0x2a02 runnable java.lang.Thread.State: RUNNABLE - locked <0x00007f515e324698> (a org.eclipse.swt.widgets.RunnableLock) - locked <0x00007f515dc6f408> (a org.eclipse.swt.widgets.RunnableLock)
1) I thought any VM/JDK should work. 2) I don't know how you call what I've seen. What I've seen is that eclipse chewed all the processing it could get until I killed it. I don't know anything about either java or eclipse internals so I can't help with the debugging other than provide some more information. You already have the java and eclipse version, the kernel version is 2.6.36.2, the distribution is Arch Linux (x86_64), I don't know what else could be relevant.
(In reply to comment #5) > 1) I thought any VM/JDK should work. Can you try with a different VM ? Sun or IBM Here are our target environments http://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_3_7.xml#target_environments
I cannot reproduce this issue. Given the age of the bug, I am going to close this. Please file a new bug against Oxygen if the issue pops up again.
