Community
Participate
Working Groups
Build Identifier: 20110916-0149 When attempting to do a project-> clean... then cleaning all projects causes Eclipse to freeze during the build and become "not responding" (rainbow spinner) on Mac OS X version 10.6.8 (MBP 8GB ram, i7 QuadCore). It frequently freezes while the process is "building" or "Validating GWT.." and random percentages. At this point I have to force quit and restart eclipse which frequently causes the issue to happen over and over as it attempts to build when eclipse is started after the initial freeze. The workspace has 80 open projects, most of which are Java / JEE Projects. I've attempted to get a thread dump, but this also does not work. I'm using a 1.6 JVM so I followed the instructions located here for using jvisualvm: http://wiki.eclipse.org/How_to_report_a_deadlock#Using_jvisualvm I'm able to do a dump while Eclipse is still responding, but am unable to get it to dump after Eclipse freezes. I'm including a thread dump 5 - 10 seconds before it locked up (by luck). I'm using Java version: java version "1.6.0_29" Java(TM) SE Runtime Environment (build 1.6.0_29-b11-402-10M3527) Java HotSpot(TM) 64-Bit Server VM (build 20.4-b02-402, mixed mode) Cleaning individual projects and building them works fine. It's when I attempt to clean all and build all projects. I'm including my eclipse.ini for reference. Reproducible: Always Steps to Reproduce: 1. Start Eclipse 2. Project -> clean ... , clean all projects 3. After cleaning, then build starts it's a matter of time before it freezes.
Does this only happen when you write GWT code? (In reply to comment #0) > I'm able to do a dump while Eclipse is still responding, but am unable to get > it to dump after Eclipse freezes. I'm including a thread dump 5 - 10 seconds > before it locked up (by luck). There is nothing attached to this bug.
Created attachment 207166 [details] Thread dump seconds before freeze
Created attachment 207167 [details] Eclipse ini for Mac OS X
I've attached two files to this bug. This does not only happen with GWT. In fact when I'm working on a workspace that has a smaller number of projects say 5 or so including GWT projects everything works fine. (In reply to comment #1) > Does this only happen when you write GWT code? > > (In reply to comment #0) > > I'm able to do a dump while Eclipse is still responding, but am unable to get > > it to dump after Eclipse freezes. I'm including a thread dump 5 - 10 seconds > > before it locked up (by luck). > > There is nothing attached to this bug.
Does the problem occur if your Eclipse installation doesn't have GWT installed? I see GWT doing work in your thread dump.
Created attachment 207170 [details] Thread dump with NO GWT Plugin installed
I removed the GPE Google Plugin for Eclipse and everything compiles without locking up the system. Unfortunately our application uses GWT so it's not really a working solution. I've also included a thread dump during a compile without GWT. (In reply to comment #5) > Does the problem occur if your Eclipse installation doesn't have GWT installed? > I see GWT doing work in your thread dump.
Do your coworkers have this problem?
No, but I'm the only one using a Mac to compile our code. The rest of our development shop is using primarily Windows, with a few using Linux. When I was using Linux I was not having this problem either. The issue has to be specific to Mac OS. (In reply to comment #8) > Do your coworkers have this problem?
Also see bug 353531, bug 355824, and bug 362448.
Created attachment 210008 [details] Thread dump seconds before freeze 2
20110916-0149 Mac OS X 10.7 I have the same problem. It repeats randomly, but the most common cases are: 1) save java file (there are some save actions) 2) svn synchronization I've attached 'Thread dump seconds before freeze', may be I am wrong but it looks like the root cause is in "Worker-258" prio=5 tid=111e97000 nid=0x150816000 waiting for monitor entry [150815000] java.lang.Thread.State: BLOCKED (on object monitor) at org.eclipse.core.internal.watson.ElementTree.includes(ElementTree.java:527) - locked <78c32e338> (a org.eclipse.core.internal.watson.ElementTree) at org.eclipse.core.internal.resources.Workspace.getResourceInfo(Workspace.java:1768) "Worker-259" prio=5 tid=114889000 nid=0x150919000 waiting for monitor entry [150917000] java.lang.Thread.State: BLOCKED (on object monitor) at org.eclipse.core.internal.watson.ElementTree.includes(ElementTree.java:527) - locked <78c32e338> (a org.eclipse.core.internal.watson.ElementTree) at org.eclipse.core.internal.resources.Workspace.getResourceInfo(Workspace.java:1768)
I've got the same problem with Lion (OS X 10.7.2) and Indigo (Build id 20110916-0149). It usually occurs during the "cleaning all projects" phase of a clean build. I've got maven and git plugins installed and it is a maven build with multiple projects.
*** Bug 371588 has been marked as a duplicate of this bug. ***
I am having similar issues. Here is my environment: Eclipse IDE for Java Developers Version: Luna Service Release 2 (4.4.2) Build id: 20150219-0600 Mac: OS X Yosemite Version 10.10.2 We have a fairly large multi-module maven project and fairly frequently when I change some code and try to save the environment freezes and I have to force shut-down. I also have the issue doing SVN synchronizations. We are using Vaadin, hence GWT, but otherwise we have a fairly lean eclipse install. I have attached a screenshot of the plugins we are using and copy of the eclipse log. I know this was an issue in Luna SP! that was supposedly fixed, but SP2 seems to be worse for me than SP!. Other members of the team are experiencing the same issue, some are using Windows boxes, so it doesn't appear to be Mac specific. Let me know if I can capture additional info that will help solve this problem, it has become a serious blocker for my team!!! I noticed this bug was filed a long time ago, but rather than create a dupe I'm adding to it. It doesn't appear to be very active, so I guess I shouldn't hold my breath for a reply or fix? Any suggestions as to cause or work arounds would be greatly appreciated.
Created attachment 253510 [details] Eclipse log. This is the eclipse log from the eclipse session where the problem occurred.
Created attachment 253511 [details] Eclipse plugins being used. This is a screen shot of the eclipse plugins we are using.
Is this problem still reproducible?
It's been years since I've seen it happen.
Thanks, closing.
