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

问题描述

几天前我刚刚将我的 Ubuntu 升级到 14.04，并在此过程中从 32 位切换到了 64 位.从那以后，Eclipse 变得非常不稳定.运行几分钟后，它会开始随机冻结越来越长的时间，特别是在代码完成时(已经不得不禁用它)，还有剪切/粘贴，偶尔保存，有时没有明显原因全部.在冻结期间，它将两个 CPU 都泵到 100%.有时它会返回好像什么也没发生过一样，有时它会抛出关于内存不足、超时或超过 GC 开销的错误.

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.

我已经按照 SO 上处理此问题的任何线程中的建议将其 Xmx 增加到 2GB，但它没有帮助.实际上，它们中建议的所有内容都没有.

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.

我正在使用 Nodeclipse、Android Developer Tools、Subversive 和 SQLExplorer 运行 Kepler.在升级之前，这种确切的设置完美无缺.

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.

更新

我已经下载了 Eclipse 的 x86 版本以及 Oracle Java 8 以及它在启动时抱怨的任何缺失的库，事实证明这更加稳定.它仍然冻结在内容辅助上，但除此之外，到目前为止它似乎很稳定.所以这肯定是 64 位版本的某种问题.

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:

• 通过 eclipse.ini 中的 Xmx 设置将内存增加到 2GB
• 在 eclipse.ini 中添加了 -Dorg.eclipse.swt.browser.DefaultType=mozilla
• 不同的 JVM:OpenJDK 7、Oracle Java 7 和 8
• 全新安装 Eclipse

我现在在 bugs.eclipse.org 上提交了一个错误:错误报告

I have now filed a bug on bugs.eclipse.org: bug report

更新 2

似乎自从安装了 32 位版本的 Eclipse(我早就又删除了)之后，64 位版本的运行也更加稳定.这对我来说真的没有意义，但在过去的几天里，它并没有冻结一次.有人可以确认吗?

没关系......它仍在做:(

此外，对于遇到此问题的其他人，如果您能在 bugs.eclipse.org 上的错误报告，因为到目前为止它在那里得到的关注为零.

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.

更新 3

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

Some more things I have tried without success:

• 根据 https://bugs.eclipse.org/bugs/show_bug.cgi?id=404776#c22
• 切换到不同的主题
• 使用环境变量运行GDK_NATIVE_WINDOWS=true
• 使用环境变量运行LIBOVERLAY_SCROLLBAR=0
• 已禁用标记出现次数"功能

• 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，很久以后

显然这不是 Eclipse 本身的错误，而是 JSDT 中的错误.根据错误报告，它已针对 3.7 版修复，在安装新的 Eclipse Mars 后，我无法确认 - 它和以往一样糟糕.但是，由于其他一些错误，新的 Eclipse 现在一直以 100% 的速度运行我的 CPU(对电池寿命不利，那...)，我决定不再将它用于我的 JavaScript 项目，至少在一段时间内尽管.

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.

问题:任何遭受此错误的人都可以确认它在 JSDT 3.7 中消失了吗?

Question: Can anyone suffering from this bug confirm it disappeared with JSDT 3.7?

更新 5，经过 LONGLONGLONGLONG 时间

由于这个问题显然不断被人们访问，我想提供最后的更新.该错误终于在一段时间后开始引起人们的注意，但前两个更新并没有为我(显然还有其他一些人)解决这个问题.由于 Eclipse 在当前状态下完全无法用于 Javascript 开发，因此我最终放弃了它.然而，人们仍然在错误报告中抱怨这个，所以我假设它仍然没有修复.我现在正在使用 Sublime Text - 很高兴，但也有一丝悲伤.我真的很喜欢 Eclipse.如果这个问题永远消失，我很高兴听到它.

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.

推荐答案

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

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屋！