Community
Participate
Working Groups
I use Eclipse 3.2 on Ubuntu Linux: Eclipse Version: 3.2.0 ; Build id: M20060629-1905 Ubuntu 6.06 LTS (kernel 2.6.15-26-686) Gnome 2.14.3 I run it with the following command line: -vmargs -Xms128M -Xmx512M Java version: java version "1.5.0_06" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05) Java HotSpot(TM) Client VM (build 1.5.0_06-b05, mixed mode, sharing) I have a number of plugins installed, including: JST, WST, Java SVN, EMF, GEF. I use Eclipse as my primary tool as a developer. However, it frequently hangs. This occurs at least once per day, sometimes more often. Each time, the UI becomes completely unresponsive. I ultimately must terminate it with a Force-quit or kill -9. There does not seem to be a consistent way to cause it to hang. The activity being performed at the time of hanging has varied. While I haven't kept track, I've noticed it hang soon after pressing CTRL+SHIFT+T in a java editor (to find a type); running an Ant build; renaming a resource. There were no messages in the log file indicating an issue. I ran it in a console and captured the thread dump. I will attach those thread dumps. I've read a number of open box regarding out-of-memory errors, but couldn't find one that described a complete hang of eclipse. However, based on those issues I did increase my permgen space. My command line is now: -vmargs -Xms128M -Xmx512M -XX:MaxPermSize=128M After one full day, Eclipse has not locked up. I'm hoping this has fixed the problem.
Created attachment 47489 [details] Archive containing 3 thread dumps while Eclipse is hanging Attached archive of 3 thread dumps. Taken a couple of minutes apart, while Eclipse was hanging (UI was unresponsive). Ultimately had to Force-quit it.
We are having the same problem. Frequent hangs on arbitrary user actions. Hangs for hours, Eclipse-UI not usable. CPU usage sometime 100%. No logs. We were using the args: -vmargs -Xmx256m so far. As Tim suggestet we will try -vmargs -Xmx512m now.
BTW we are using win XP.
John, could you have a quick look at the Thread dump logs? There seem to be a lot of: "Framework Event Dispatcher" daemon prio=1 tid=0x083d8068 nid=0x46ca in Object.wait() [0xb1d98000..0xb1d98e30] at java.lang.Object.wait(Native Method) - waiting on <0x6f1d0078> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread) at java.lang.Object.wait(Object.java:474) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.getNextEvent(EventManager.java:349) - locked <0x6f1d0078> (a org.eclipse.osgi.framework.eventmgr.EventManager$EventThread) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:287) Where it's locked <0x6f1d0078> and then is waiting on <0x6f1d0078> (they're in a number of IO threads as well). PW
*** This bug has been marked as a duplicate of 92250 ***
(In reply to comment #2) Note that it is the "-XX:MaxPermSize" that is key here. See the linked duplicate 92250 from Comment #5 for more info.
reopening
Sorry for the spam... since bug 92250 refers to crashes and OOME's rather than a hang, I have created a new bug to cover this. *** This bug has been marked as a duplicate of 153485 ***
