Eclipse Kepler freezes on 64 bit ubuntu
I just upgraded my Ubuntu to 14.04 a few days ago and in the process switched from 32 to 64 bits. Ever since, Eclipse has gotten really unstable. After having run for a few minutes it will start randomly freezing for longer and longer periods of time, particularly on code completion (already had to disable that), but also on cut/pasting, occasionally on saving, and sometimes for no apparent reason at all. During the freezes it pumps both CPUs to 100%. Sometimes it then comes back as if nothing had happened, sometimes it'll spout errors about being out of memory, timing out or exceeding the GC overhead.
I've already increased its Xmx to 2GB as suggested in any thread dealing with this issue here on SO, but it hasn't helped. Actually, none of the things suggested in them have.
I'm running Kepler with Nodeclipse, Android Developer Tools, Subversive and SQLExplorer. That exact setup worked flawlessly before the upgrade.
Can anyone confirm this issue or (hope dies last) suggest a fix? If anyone else has this too I'll file a bug.
UPDATE
I have downloaded an x86 version of Eclipse as well as Oracle Java 8 and any missing libraries it was complaining about when starting, and this has proven a lot more stable. It still freezes on content assist, but other than that, it seems stable so far. So it must definitely be some kind of issue with the 64 bit version.
To sum up all the things already tried and uneffective at this point:
- Increased memory to 2GB through Xmx setting in eclipse.ini
- Added
-Dorg.eclipse.swt.browser.DefaultType=mozillato eclipse.ini - Different JVMs: OpenJDK 7, Oracle Java 7 and 8
- Fresh install of Eclipse
I have now filed a bug on bugs.eclipse.org: bug report
UPDATE 2
It seems that ever since having installed the 32 bit version of Eclipse (which I have long since deleted again), the 64 bit version is also running more stable. This doesn't really make sense to me, but over the last few days, it hasn't frozen up once. Can anyone confirm?
Never mind...it's still doing it :(
Also, for anyone else having this problem, I'd appreciate it if you could post 'me too' on the bug report on bugs.eclipse.org as it has gotten zero attention there so far.
UPDATE 3
Some more things I have tried without success:
- Added
-Dorg.eclipse.swt.browser.XULRunnerPath=/dev/nullto eclipse.ini as per https://bugs.eclipse.org/bugs/show_bug.cgi?id=404776#c22 - Switched to different themes
- Ran with environment variable
GDK_NATIVE_WINDOWS=true - Ran with environment variable
LIBOVERLAY_SCROLLBAR=0 - Disabled "mark occurences" feature
UPDATE 4, after a long long time
Apparently this is not a bug in Eclipse itself, but in JSDT. According to the bug report, it's fixed for version 3.7, which, after an install of the new Eclipse Mars, I cannot confirm - it's just as bad as ever. But since, from some other bug, the new Eclipse is now constantly running my CPU at 100% (bad for battery life, that...), I have decided to move away from using it for my JavaScript projects, at least for a while.
Question: Can anyone suffering from this bug confirm it disappeared with JSDT 3.7?
UPDATE 5, after a LONGLONGLONGLONG time
Since this question apparently keeps being visited by people I want to give a final update. The bug finally started getting attention a while back, the first two updates however didn't fix the issue for me (and apparently some other people). As Eclipse was entirely unusable for Javascript development in its current state, I finally gave up on it. People are still complaining about this on the bug report, however, so I'm assuming it's still not fixed. I am now using Sublime Text - quite happily, but also with a twinge of sadness. I really liked Eclipse. If this issue ever goes away for good, I'd appreciate to hear about it.
Answer
Had the same problem for a few days. Added the following line in the end of eclipse.ini and it solved for me:
-Dorg.eclipse.swt.browser.DefaultType=mozilla