Community
Participate
Working Groups
Build Identifier: 20100917-0705 Eclipse's UI often locks up, with 1 CPU at 100%. Thread dumps consistently show an active worker thread that seems to be scanning jars, presumably doing some kind of jsp taglib indexing, as suggested by the following stacktrace fragment (I'll attach a full thread dump too): java.lang.Thread.State: RUNNABLE at java.util.zip.Inflater.inflateBytes(Native Method) at java.util.zip.Inflater.inflate(Inflater.java:238) - locked <0x00007f455410a050> (a java.util.zip.ZStreamRef) at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:135) at java.util.zip.ZipInputStream.read(ZipInputStream.java:154) at java.util.zip.ZipInputStream.closeEntry(ZipInputStream.java:100) at java.util.zip.ZipInputStream.getNextEntry(ZipInputStream.java:78) at org.eclipse.jst.jsp.core.taglib.ProjectDescription.updateJAR(ProjectDescription.java:2268) at org.eclipse.jst.jsp.core.taglib.ProjectDescription$Indexer.visit(ProjectDescription.java:217) at org.eclipse.core.internal.resources.Resource$1.visitElement(Resource.java:64) at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:82) at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86) at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86) at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86) at org.eclipse.core.internal.watson.ElementTreeIterator.doIteration(ElementTreeIterator.java:86) at org.eclipse.core.internal.watson.ElementTreeIterator.iterate(ElementTreeIterator.java:127) at org.eclipse.core.internal.resources.Resource.accept(Resource.java:74) at org.eclipse.jst.jsp.core.taglib.ProjectDescription.index(ProjectDescription.java:1417) at org.eclipse.jst.jsp.core.taglib.ProjectDescription.restoreReferences(ProjectDescription.java:1906) at org.eclipse.jst.jsp.core.taglib.ProjectDescription.<init>(ProjectDescription.java:670) at org.eclipse.jst.jsp.core.taglib.TaglibIndex.createDescription(TaglibIndex.java:757) at org.eclipse.jst.jsp.core.taglib.TaglibIndex.internalResolve(TaglibIndex.java:937) at org.eclipse.jst.jsp.core.taglib.TaglibIndex.resolve(TaglibIndex.java:578) [...] This happens routinely, and all I can do is kill the process and restart Eclipse. I haven't yet re-created the hang with a clean workspace. It's possible this is a conflict with other plugins - I'll attach my full installation details and .log. Reproducible: Sometimes Steps to Reproduce: I haven't identified a pattern to reproduce. It happens every 5-45 minutes, regardless of what I'm doing with Eclipse.
Created attachment 187398 [details] Log file at point of hang
Created attachment 187400 [details] Thread dump at point of hang
Created attachment 187401 [details] Another thread dump at point of separate hang
Created attachment 187402 [details] Installation details.
Looks like it is duplicate of Bug 321602.
Hi Robin, Thanks for your report. Rakesh is right, this looks to be a duplicate of Bug 321602. We have a fix lined up for Service Release 2 of Helios. But, in the meantime, you should be able to apply the feature patch that is attached to Bug 321602 comment 10. Follow those instructions and you should have everything cleared up. Bug 321602 comment 20 also has some alternate steps if you get stuck with the ones in 10. *** This bug has been marked as a duplicate of bug 321602 ***
