Eclipse Kepler在64位ubuntu上冻结 [英] Eclipse Kepler freezes on 64 bit ubuntu

问题描述

我刚刚将Ubuntu升级到14.04，在这个过程中，从32位切换到64位。从此以后，Eclipse已经变得非常不稳定了。运行了几分钟后，它会开始随机冻结更长时间，特别是在代码完成（已经不得不禁用）的情况下，而且还要剪切/粘贴，偶尔保存，有时候没有明显的理由所有。在冻结期间，它将两个CPU泵送到100％。有时它会回来，就好像没有发生任何事情，有时候会发出关于内存不足，超时或超出GC开销的错误。

我已经将其Xmx增加到2GB，如在SO处理这个问题的任何线程中所建议的，但它没有帮助。实际上，没有一个建议的东西。

我正在运行Kepler与Nodeclipse，Android开发工具，Subversive和SQLExplorer。这个确切的设置在升级之前完美无瑕。

任何人都可以确认这个问题，或者（希望死于最后）建议修复？如果还有其他人也会提出错误。

更新

我已经下载了一个x86版本的Eclipse以及Oracle Java 8以及它在启动时所抱怨的任何缺少的库，而且已经证明了更加稳定。它仍然冻结内容协助，但除此之外，它似乎稳定到目前为止。所以它肯定是64位版本的一些问题。

总结已经尝试过的所有事情，这一点不起作用：

• 通过eclipse.ini中的Xmx设置将内存增加到2GB


• 添加了 -Dorg.eclipse。 swt.browser.DefaultType = mozilla to eclipse.ini


• 不同的JVM：OpenJDK 7，Oracle Java 7和8


• 新鲜安装的Eclipse

我现在提交了bugs.eclipse.org的错误：错误报告

更新2

似乎从安装了32位版本的Eclipse（我已经再次删除了），64位版本也是运行更稳定。这对我来说真的没有意义，但在过去的几天里，它还没有冻结一次。有人可以确认吗？

没关系...它还在做：（

另外，对于任何有这个问题的人，如果你也可以在 bugs.eclipse.org的错误报告，因为目前为止已经没有关注。

更新3

还有一些我没有成功尝试的事情：

• 根据 -Dorg.eclipse.swt.browser.XULRunnerPath = / dev / null bug / show_bug.cgi？id = 404776＃c22rel =nofollow noreferrer> https://bugs.eclipse.org/bugs/show_bug.cgi?id=404776#c22


• 切换到不同的主题


• 带有环境变量 GDK_NATIVE_WINDOWS = true


• 环境变量 LIBOVERLAY_SCROLLBAR = 0


• 禁用标记发生功能

更新4，经过很长时间

<显然这不是Eclipse本身的一个bug，而是在JSDT中。根据错误报告，它已经针对版本3.7修复，在安装新的Eclipse Mars之后，我无法确认 - 它与以前一样糟糕。但是，由于从其他一些错误，新的Eclipse现在不断运行我的CPU在100％（坏的电池寿命，那...），我已经决定放弃使用它为我的JavaScript项目，至少对于一个而。

问题：任何患有此错误的人都可以通过JSDT 3.7确认消失？

更新5之后，长龙龙时间

由于这个问题显然不断被人访问，我想给予最后的更新。这个bug终于开始引起注意了，但是前两个更新没有解决我的问题（显然还有一些其他人）。由于Eclipse在当前状态下完全不可用于Javascript开发，所以我终于放弃了。然而，人们仍然在错误报告中抱怨这一点，所以我假设它仍然不是固定的。我现在正在使用崇高的文本 - 很高兴，但也有一丝悲伤。我真的很喜欢Eclipse。如果这个问题已经消失，我很乐意听到。

解决方案

有几个同样的问题天。在eclipse.ini结尾添加了以下行，它为我解决了：

  -Dorg.eclipse.swt.browser。 DefaultType = mozilla 
  

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=mozilla to 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/null to 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.

解决方案

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

这篇关于Eclipse Kepler在64位ubuntu上冻结的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！