Community
Participate
Working Groups
Build Identifier: Version: Helios Release, Build id: 20100617-1415 I just started Eclipse. Settings: eclipse.exe -vm "%JAVA_HOME%"\bin -vmargs -DsuppressRawWhenUnchecked=true In the initialize phase it doesn't show any progress. In the right hand corner it shows: Initializing Java Tooling: (1%) The Progress tab shows empty bars: Initializing Java Tooling Initializing JavaScript Tooling Loading Web Service DOM... (Waiting) Java: java version "1.6.0_21" Java(TM) SE Runtime Environment (build 1.6.0_21-b07) Java HotSpot(TM) Client VM (build 17.0-b17, mixed mode, sharing) The eclipse process takes 50% CPU time. I'm not sure whether it is reproducible or not, but unfortunately, today it has been three times on a row before I decided to file this bug. Even a -clean didn't solve the issue - so at the moment it seems reproducible. I will attach the stack trace. Reproducible: Always Steps to Reproduce: 1. Startup
Created attachment 192068 [details] Stack trace
I was able to start another workspace. The workspace that couldn't be started has around 15 open real world projects, as the other workspace has only that number of test projects.
This seems to be caused by a lock in the class DependencyGraphImpl from wst.common: java.lang.Thread.State: BLOCKED (on object monitor) at java.lang.Object.wait(Native Method) at org.eclipse.core.internal.jobs.Semaphore.acquire(Semaphore.java:39) - locked <0x18446270> (a org.eclipse.core.internal.jobs.Semaphore) at org.eclipse.core.internal.jobs.OrderedLock.doAcquire(OrderedLock.java:176) at org.eclipse.core.internal.jobs.OrderedLock.acquire(OrderedLock.java:110) at org.eclipse.wst.common.componentcore.internal.builder.DependencyGraphImpl.waitForAllUpdates(DependencyGraphImpl.java:667)
Strangely this doesn't actually appear to be deadlocked. Waiting is Worker 10: "Worker-10" prio=6 tid=0x05c2bc00 nid=0x1b80 in Object.wait() [0x0a5ae000] java.lang.Thread.State: BLOCKED (on object monitor) at java.lang.Object.wait(Native Method) at org.eclipse.core.internal.jobs.Semaphore.acquire(Semaphore.java:39) - locked <0x18446270> (a org.eclipse.core.internal.jobs.Semaphore) However Worker-9 is in the middle of releasing that exact lock: "Worker-9" prio=6 tid=0x05c2b400 nid=0x638 runnable [0x0a2af000] java.lang.Thread.State: RUNNABLE at java.lang.Object.notifyAll(Native Method) at org.eclipse.core.internal.jobs.Semaphore.release(Semaphore.java:66) - locked <0x18446270> (a org.eclipse.core.internal.jobs.Semaphore) This implies either 1) you are not deadlocked and maybe it is just taking longer than you expected 2) The VM itself is somehow blocked in the Object.notifyAll() native code. This would be a VM bug, but fairly surprising. You may want to try running with a different VM version to rule that out.
(In reply to comment #4) > This implies either > > 1) you are not deadlocked and maybe it is just taking longer than you expected > 2) The VM itself is somehow blocked in the Object.notifyAll() native code. This > would be a VM bug, but fairly surprising. You may want to try running with a > different VM version to rule that out. I appreciate your efforts. I have waited more than half an hour to rule out that it was my impatience. So I'm pretty sure the system is kind of deadlocked. In the jvisualvm, I saw a frequent start and stop on one thread, as another one was green all the time (working), and the others were yellow (waiting). The system was still more or less responsive, that is to say I could select Windows preferences for example. However, when I tried to do something in Java code, the whole system became 'foggy' and there was nothing more I could do but using the task manager to close eclipse. In the end, I might have touched the JDT Weaving setting, as the last time I started the system again I got again the question whether to enable weaving or not. I didn't restart eclipse after that question and am able to work in the workspace for now.
This looks like the bug that was fixed for Helios SR2. Your build identifier indicates that you are using Helios GA. Can you update to SR2 and see if you can reproduce the problem? If you can reproduce this with SR2, please reopen this bug. *** This bug has been marked as a duplicate of bug 327801 ***
> Can you update to SR2 and see if you > can reproduce the problem? If you can reproduce this with SR2, please reopen > this bug. I'll do that. Sorry for duplicating a bug. Thanks!
Unfortunately, this morning I'm facing (almost) the same problem again. Eclipse is more than half an hour in the Initializing Java Tooling phase (showing 1%). I'm now on the updated version: Version: Helios Service Release 2 Build id: 20110301-1815 The Progress tab shows the same three empty bars: Initializing Java Tooling Initializing JavaScript Tooling Loading Web Service DOM... (Waiting) The eclipse process takes approximately 50% CPU time. The main difference with the previous reported situation seems to be that the system is kind of responsive to input. When I press [CTRL] [SHIFT] T (open Type), the dialog appears (but with an extra line 'Initializing search indices: 1 operation remaining.' , and I'm able to type something in it, but I will never see Matching items. But I am able to close the dialog again, and reopen it, without freezing Eclipse. I don't remember I could do such a thing the previous time. I tried again restarting, even with a clean, without much luck, but after disabling the weaving and restarting, Eclipse was functioning again. Hope this helps in tracking down the bug. I'll also add a stacktrace.
Created attachment 192702 [details] Stack trace
Niek, from the stack trace that you sent, it looks like your WTP was not updated to Helios SR2. Can you please check the version of your org.eclipse.wst.common.modulecore plugin? It should be 1.2.5.v201101270100
(In reply to comment #10) > org.eclipse.wst.common.modulecore plugin? It should be 1.2.5.v201101270100 That's right. It is 1.2.3.v201008242000. I'm not the guy that installs all the available updates. Is there a way to see which updates are related? Thanks!
(In reply to comment #11) > (In reply to comment #10) > > org.eclipse.wst.common.modulecore plugin? It should be 1.2.5.v201101270100 As a matter of fact, I don't see this as an Available Update listed (or maybe I don't look at the right place). What is the preferred way of doing this update?
Moving this to releng, since it is a setup of the Update site issue.
Sorry for not noticing this sooner ... but doubt it's an "update site issue" per se. Whether or not "check for updates ..." finds anything depends a great deal on what you installed, how you installed it, etc. So ... you can always try "install new software" and get the latest versions of "Web Tools" features from the helios repository. Hope that helps,
Since David answered the question "What is the preferred way of doing this update?", and since there has been no more discussion since, I am going to resolve this issue.
