Community
Participate
Working Groups
Build Identifier: 20110615-0604 I'm seeing the UI lock up (Spinner icon) about once every 1-2 hours, especially when attempting to use refactoring to rename a variable. This is under OS X Snow Leopard. I attempted to debug the problem by running Eclipse under the Eclipse debugger as suggested in the FAQ. However, once the problem occurred the debugger was not able to communicated with the child process - any attempt to pause the running program gave an error message about packets timing out. I have an error dump produced by the OS X "Force Quit" dialog, which I will attach. Reproducible: Sometimes
Created attachment 201466 [details] Stack dump from Apple's 'force quit' dialog.
Please get a thread dump from VisualVM when Eclipse is locked up.
(In reply to comment #1) > Created attachment 201466 [details] > Stack dump from Apple's 'force quit' dialog. Actually, it looks to be stuck in some UI work.
Created attachment 201637 [details] VisualVM Tread tab on lock-up (Thread Dump failing) OS: Snow Leopard 10.6.8 Eclipse IDE for C/C++ Developers Version: Indigo Release Build id: 20110615-0604 java.version=1.6.0_26 java.vendor=Apple Inc. Eclipse locked-up (beachballing). Attempting a VM thread dump but failing.
I am experiencing what I believe is the same bug, my args: -vmargs -Dosgi.requiredJavaVersion=1.6.0 -XstartOnFirstThread -Dorg.eclipse.swt.internal.carbon.smallFonts -XX:MaxPermSize=384m -Xms128m -Xmx1024m -Xdock:icon=../Resources/Eclipse.icns -XstartOnFirstThread -Dorg.eclipse.swt.internal.carbon.smallFonts -XX:+HeapDumpOnOutOfMemoryError -Dcom.sun.management.jmxremote Also seems to beachball after 1-2 hours, usually after UI updates e.g. auto-complete proposal / syntax error highlighting etc. Force quit required. No errors apparent in eclipse error log. No heap dump written. Have tried a VM thread dump when it occurs but it fails, please see screenshot.
Created attachment 203062 [details] Same problem experienced when using Helios. I have tried downgrading to Helios and the same problem occurs, which suggests that it's probably not an Eclipse bug. Nonetheless any suggestions would be welcomed. Apple crash report for Helios attached.
OK so I was finally able to reproduce the lockup when running under VisualVM. Unfortunately, attempting to get a thread dump did not work. VisualVM is still responsive to user interaction, but it's been 10 minutes and the "Getting Thread Dump..." progress bar has not moved.
By the way, this is still happening for me - eclipse locks up about once an hour. And as mentioned in the previous note, running under visualvm did not provide any useful information.
I too am experiencing what appears to be the same bug, and it makes eclipse virtually unusable in OS X..
GIven the lack of good data on this bug - is there some alternate JVM that I could perhaps try running Eclipse under to see if I can get better data?
I went ahead and installed OpenJDK and updated my eclipse.ini file with the -vm arg to use it. I've been using that for 3 days and so far only one lockup, which is a tremendous improvement from before - previously I was getting 1-2 lockups per hour of us. The one lockup I did get was during a multi-file rename.
Created attachment 205271 [details] Stack dump from Apple's 'force quit' dialog, under OpenJDK Here's a new stack dump taken from the "force quit" dialog. The difference between this stack dump and the previous one is that this one was taken while running Eclipse under OpenJDK instead of the default JDK that comes with Snow Leopard. I'm hoping that this may help to shed some additional light on the problem. Note that I'm still experiencing what I reported in the previous message - under OpenJDK, the lockups occur much less frequently, about once every 3-4 days, as opposed to 1-2 times per hour with the default JDK - but they still occur.
Created attachment 205479 [details] Stack dump from Apple's 'force quit' dialog, rename variable. Here's another thread dump taken from the "force quit" dialog. This was taken after Eclipse froze when attempting to rename a variable using the "Rename" refactoring command. As I mentioned, Eclipse seems to freeze ("spinning beach ball") about once per day when running under OpenJDK, and much more frequently when running under the default JDK. This is with normal usage, i.e. typing, saving, running "make", etc. However, the "Rename..." menu seems to lock up virtually 100% of the time. This may be a different bug, which is why I'm submitting this stack dump in addition to the others. I'm also curious to know if there is a more recent version of Eclipse that I should be trying. The version that I am currently running is build ID 20110615-0604, which is several months old at least. This was downloaded from the Eclipse Indigo download page - I generally only install pre-built binary packages, as attempting to build from source is way too complex and time-consuming for me. Unfortunately, the Eclipse Indigo download page gives absolutely no indication what version is being downloaded - in other words, there's no way to determine if the version available from the download page is different than the version that I am currently running, other than actually downloading and installing it. And I'm loathe to re-install Eclipse unless there's some compelling reason to do so, since reinstalling and reconfiguring all of my plugins is a pain. Mainly, I'd like to know if there is some other version that I should be testing in order to provide better data about this problem.
(In reply to comment #13) You need not build from source. You can try a more recent build (either 3.7.1 or 3.8M2) from here --> http://download.eclipse.org/eclipse/downloads/eclipse3x.php and see if the problem still happens.
I installed 3.7.1 and I have not had a crash since then, even when doing refactoring operations.
Created attachment 205778 [details] Another dump from force quit dialog I got another freeze with 3.7.1, this was after about a week's worth of use (say, around 25 hours of use doing normal editing of C++ code and various refactoring.) I've attached the dump again.
Created attachment 209767 [details] .log file showing some codan errors Just wondering if anyone has had any progress with this bug, I'm still suffering a three or four crashes daily. I've tried the latest version of Indigo, also tried reverting to Helios which was marginally better but still crashed once a day. Tried different Java updates (0_26 and 0_29), tried increasing the virtual memory, tried adding the "-UseCompressedOops", tried to get a VisualVM thread dump but it fails to get anything. Tried switching Applications > Utilities > JavaPreferences to 32bit preferred but none of these things made any improvements really (some made things worse). Tried disabling "EclipsePrefs > Code Analysis > Launching > As you type", no luck. I have a hunch that one of the Code Analysis / Checker tools is involved the issues, as the log file indicates (attached). It shows errors around start-up, but not any from around the time of the crash (I assume that maybe in its frozen state it is unable to write to the log file). Just don't know what to try next! Any suggestions welcome. Thanks
Created attachment 210207 [details] VisualVM thread dump Thread dump from VisualVM while getting beachball (switching to non-visable editor tabs)
Hi I'm facing the same issue, which mostly happens when launching a Java application: eclipse get stuck in preparing the launch. Waiting for a few minutes doesn't help, eclipse remains stuck. I've to force quit and restart it. Very painful. I use the following eclipse: Eclipse Java EE IDE for Web Developers. Version: Indigo Service Release 2 Build id: 20120216-1857 My java -version is the following: java version "1.6.0_29" Java(TM) SE Runtime Environment (build 1.6.0_29-b11-402-11D50b) Java HotSpot(TM) 64-Bit Server VM (build 20.4-b02-402, mixed mode) My ini file is the following: -clean -startup ../../../plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar --launcher.library ../../../plugins/org.eclipse.equinox.launcher.cocoa.macosx.x86_64_1.1.101.v20120109-1504 -product org.eclipse.epp.package.jee.product --launcher.defaultAction openFile -showsplash org.eclipse.platform --launcher.XXMaxPermSize 256m --launcher.defaultAction openFile -vmargs -Dosgi.requiredJavaVersion=1.5 -Dorg.eclipse.swt.internal.carbon.smallFonts -XX:MaxPermSize=128m -XX:PermSize=128m -Xms1024m -Xmx1024m -Xdock:icon=../Resources/Eclipse.icns -XstartOnFirstThread I join the apple dump and a jstack done on the eclipse process. Would be very nice to have a solution for this issue. best
Created attachment 212510 [details] The stack from the Apple force quite dialog.
Created attachment 212511 [details] The stack trace from jstack
Oh, last additions: Mac OS X version 10.7.3 When stuck, eclipse was using 100% of CPU (out of 4 cores).
I'm getting the same symptoms under Juno. Juno freeze to death sometimes when I perform some operations like rename, refactor, move, delete projects, open or change views and crash 100% when I try to parse something with WindowBuilder. I first ran Java 1.7u6 then moved to Java 1.7u8 beta. I tried to dump with VisualVM but as Eclipse take 100%, it wouldn't work.
Created attachment 220091 [details] crash on relaunch after freeze Sometime (about 10-20%), when I relaunch Eclipse after it freezes, Eclipse crashes and I get this in the logs. It may be completly unrelated or just a side effect, but so far I never got it on a "normal" launch (though I had only a few "normal" launches).
posted stacktrace of a crash I sometime get on relaunch after freeze, maybe unrelated. also, often my preferences are wiped when I relaunch.
Created attachment 220092 [details] apple stack after kill when using WindowBuilder The Apple stack I get after killing Eclipse when it freezes after trying to parse some class with WindowBuilder
I don't know if this is the same issue, but I am on Snow Leopard (10.6.8 running as i386) with Juno (4.2.0) and have been experiencing hangs with Java development for a long time, including with previous Eclipse releases. The problem definitely seems to be Java-specific (e.g. when editing Python files with PyDev it does not occur). It also seems to be related to code analysis. In fact, I can nearly always reproduce by making a change that adds or removes a syntax error, and immediately entering Cmd+S to save the file. (I have learned to wait a second or two after editing the code before saving.) Various attempts to muck with eclipse.ini options have no effect. The only refactoring command I use is Rename, which has caused problems on occasion as well. Current Java version information: java version "1.6.0_35" Java(TM) SE Runtime Environment (build 1.6.0_35-b10-428-10M3811) Java HotSpot(TM) 64-Bit Server VM (build 20.10-b01-428, mixed mode)
Created attachment 230590 [details] Apple crash report on hung Eclipse Note that the crash report says: Command: Eclipse Path: /Applications/eclipse/Eclipse.app/Contents/MacOS/eclipse Version: 3.8 (3.8) whereas the actual Eclipse version is Eclipse SDK Version: 4.2.2 Build id: M20130204-1200
Created attachment 230592 [details] Eclipse (Not responding) Activity Monitor
Hangs with 100% cpu for me frequently too. Renders Eclipse completely useless. Only plug-in is PyDev. See "Apple crash report on hung Eclipse", "Eclipse (Not responding) Activity Monitor" MacBook Pro System Software Overview: System Version: Mac OS X 10.7.5 (11G63) Kernel Version: Darwin 11.4.2 Processor 2.8 GHz Intel Core i7 $ java -version java version "1.6.0_45" Java(TM) SE Runtime Environment (build 1.6.0_45-b06-451-11M4406) Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01-451, mixed mode) Eclipse SDK Version: 4.2.2 Build id: M20130204-1200
Created attachment 230598 [details] eclipse.ini
Created attachment 230599 [details] Eclipse configuration
Also tried to use Oracle's Java 7: $ "/Library/Java/JavaVirtualMachines/JDK 1.7.0 Developer Preview.jdk/Contents/Home/bin/java" -version openjdk version "1.7.0-ea" OpenJDK Runtime Environment (build 1.7.0-ea-b222) OpenJDK 64-Bit Server VM (build 21.0-b17, mixed mode) According to http://wiki.eclipse.org/Eclipse.ini, to specify the java VM, one says: -vm <java execution path> like this: -vm /Library/Java/JavaVirtualMachines/JDK 1.7.0 Developer Preview.jdk/Contents/Home/bin/java Although Eclipse starts with this (see https://bugs.eclipse.org/bugs/attachment.cgi?id=230598) the configuration remains java.version=1.6.0_45 (see https://bugs.eclipse.org/bugs/attachment.cgi?id=230599). Perhaps a distinct bug.
Any ideas folks? It doesn't look like anyone is working on this. I'd hate to abandon Eclipse, but can't use it when it freezes this frequently.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
