Community
Participate
Working Groups
Build Identifier: 20100915173744 Seems like Bug #302644 stroke again. I'm developing m2eclipse-wtp and testing it with Eclipse 3.6.1 ( Eclipse Web Developer Tools Version: 3.2.2.v201008100100-7O7CFbKEMf84nUlEJyX7-SPQjhYZ) I'm often facing an Eclipse freeze on startup. I sometimes pass the splashscreen, but then java.exe sucks 100%CPU forever. I'm attaching a few threaddumps taken under a minute. This is really painful. Only solution is to delete the workspace metadata and reimport the projects. Igor Fedorenko (https://issues.sonatype.org/browse/MNGECLIPSE-2375) pointed me to #302644. If there's anything we can do on m2eclipse' side I'd be glad to hear it. Regards, Fred Bricon Reproducible: Sometimes Steps to Reproduce: Can't reproduce it, but I can provide workspace metadata if needed.
Created attachment 180915 [details] 3 thread dumps taken during eclipse freeze
Assigning to Jason for initial investigation.
This is similar to bug 327801, for now these will be tracked separately though to ensure both scenarios are fixed. The problem is in Worker-4 at this line: org.eclipse.wst.common.componentcore.internal.resources.VirtualComponent.getRawReferences(VirtualComponent.java:401) From that line up the calls to JDT should not occur.
Actually, upon looking at bug 327801, these are identical. *** This bug has been marked as a duplicate of bug 327801 ***