Eclipse 3.6 在内容辅助期间频繁停止
自动完成功能经常停止运行并且持续很长时间，因此我完全停止使用它。
The auto complete stalls so frequently and for so long, I quit using it altogether.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
我在 Windows 7 x64 上使用 Eclipse (Classic) 3.6.1 成功完成了以下操作。
“在 3.6.2 中发布修复之前，这里总结了一种解决方法：http://groups.google .com/group/android-developers/msg/0f9d2a852e661cba”
（为了方便而复制）
“您可以替换您的/plugins/
org.eclipse.jdt.core_3.6.1.v_A68_R36x.jar 插件，其中包含一个
http://www.google.com/url?q=http://adt-addons。谷歌代码。 com/svn/patches/org.eclipse.jdt.core_3.6.1.v_A68_R36x.zip&ei=vg5aTf2RIMrUgAeI-qTvDA&sa=X&oi=unauthorizedredirect&ct=targetlink&ust=1297749446528273&usg=AFQjCNFv7 FGlTrnoVhRGE35JPjHxOwI_Bw
并重新启动 Eclipse。内容辅助会好得多。试试吧。
不要忘记备份您原来的插件。 ”
I've had success with the following using Eclipse (Classic) 3.6.1 on Windows 7 x64.
"A workaround, until the fix is released in 3.6.2 is summarized here: http://groups.google.com/group/android-developers/msg/0f9d2a852e661cba"
(copied for convenience)
"You can replace your /plugins/
org.eclipse.jdt.core_3.6.1.v_A68_R36x.jar plugin with one from
http://www.google.com/url?q=http://adt-addons.googlecode.com/svn/patches/org.eclipse.jdt.core_3.6.1.v_A68_R36x.zip&ei=vg5aTf2RIMrUgAeI-qTvDA&sa=X&oi=unauthorizedredirect&ct=targetlink&ust=1297749446528273&usg=AFQjCNFv7FGlTrnoVhRGE35JPjHxOwI_Bw
and restart Eclipse. Content Assists will be much better. Just try it.
Don't forget backup your original plugins. "
这解决了我的部分问题。
在首选项中，我默认了所有“Java->编辑器->内容辅助”屏幕，性能得到了很大提高。我现在遇到的任何延迟都是由于系统速度造成的，可以忽略不计。我花了几分钟到几秒钟来构建建议列表。
更新：这并没有完全解决我的问题，但它让我接近了。搜索继续...
更新：我正在使用包含的默认包以及更新期间可能出现的任何包在 Java for Android 中进行开发（回想起来，也许选择在 SDK 更新中全部更新可能并不明智） ）。线上线下的时间安排相当一致。我做了一些测试并发现了以下内容：
启动 Eclipse 并输入一行可以使用 .toString() 的代码。输入“.”在 2-3 秒内填充自动完成。输入“t”，需要 70-75 秒。之后，10秒。 Diff 对象做同样的事情（第一次 75，之后 10）。过滤过程似乎停滞了。我的CPU没有达到最大，内存也正常，但是程序在完成之前不会响应。任何预输入都会被缓存，并最终在 Eclipse 开始响应时过滤列表。
This solved part of my problem.
In preferences, I defaulted all the 'Java->Editor->Content assist' screens and the performance is much improved. Any lag I have now is due to system speed and is negligible. I've gone from minutes to seconds building the suggestion list.
UPDATE: This didn't completely solve my problem, but it got me close. The search continues...
UPDATE: I'm developing in Java for Android using the default packages that are included and any that might have come down during a update(in retrospect, maybe choosing update all in the SDk update might not have been wise). The timing is fairly consistent online and offline. I did a few tests and found the following:
Startup Eclipse and enter a line of code that can use a .toString(). Typing the '.' populates the auto complete within 2-3 seconds. Type a 't' and it takes 70-75 seconds. After that, 10 seconds. Diff objects do the same thing(75 the first time, 10 after that). It's the filtering process that appears to stall. My CPU does not max, Memory is OK, but the program will go not responding till it's done. Any typeahead gets cached and eventually filters the list when Eclipse starts responding.
对我来说，当我增加虚拟机的内存时，问题就消失了。
将其放入您的 eclipse.ini 中：
For me the problem went away when I increased the memory for the vm.
Put this in your eclipse.ini:
在我的 4GB Windows Vista 系统上，这种情况经常发生！ （以及查找变量时的调试问题）。
在我组装了 8GB RAM 的新电脑后，这一切都消失了。我现在可以同时运行 4 个模拟器，而且也不再有任何调试问题。自动完成巨大的列表也可以正常工作。
这似乎只是你有多少内存的问题。
on my 4GB Windows Vista system this would happen A LOT !! (as well as debug issues when looking up variables).
This all went away after I built my new PC with 8GB RAM. I can now run 4 emulators simultaneously and it doesn't have any debug problems any more either. Auto complete with huge lists also works just fine.
it would seem to be just an issue with how much RAM you've got.