Eclipse ContentAssist 突然非常非常慢
由于不值得在此讨论的原因，我在 Eclipse 下进行 Android 开发时严重依赖 ContentAssist。当我去年夏天第一次开始使用它时，我让 Ganymede 在旧的、缓慢的 XP 系统上运行，当我引用具有大型继承层次结构和许多方法的对象（例如、Android 视图类型、上下文等）。
为了让生活更轻松，我将 PC 升级到了新的四核系统，内存为 8Gb，运行 Windows 7 Pro，Eclipse 运行起来就像闪电一样；问题解决了，至少我是这么想的。
有一天，一切似乎突然又变慢了，当我引用复杂对象时，ContentAssist 再次挂起几秒钟。我最近所做的唯一更改是将我的开发环境升级到最新的 Android SDK 和工具集，并安装 Eclipse Helios。
那么是 Helios 升级造成的吗？我几周前升级了，但最近当我开始做一堆新的开发工作时才注意到这一点。如果我不明白这个问题，我该怎么做才能回到木卫三？
Possible Duplicate:
Eclipse Android SDK slow Content Assist performance
For reasons not worth discussing here, I rely heavily on ContentAssist in my Android development under Eclipse. When I first starting using it last summer, I had Ganymede running on an old, slow XP system and ContentAssist would effectively lock everything up for 10-20 seconds or more when I was referencing an object with a large inheritance hierarchy and many methods (e.g., types of Android Views, Context, etc.).
To make life easier I upgraded my PC to a new quad-core system with 8Gb memory running Windows 7 Pro, and Eclipse then ran like lightning; problem solved, or so I thought.
The other day, everything suddenly seemed to have slowed down again, to the point where ContentAssist is again hanging up for several seconds at a time when I reference complex objects. The only recent changes that I have made have been to upgrade my development environment to the latest Android SDK and toolset, plus installing Eclipse Helios.
So is it the Helios upgrade that did it? I upgraded a few weeks ago, but I just noticed this recently when I started doing a bunch of new development work. What would I have to do to go back to Ganymede if I can't figure this out?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
几周前我遇到了这样的问题，这是由于 ADT 向 Eclipse 提供了一些有关 Android 源代码在类路径中的位置的无效信息。我通过下载 Android 源代码并自己附加它们来修复它。该错误在这里：
http://code.google.com/p/ android/issues/detail?id=7850
以及有关如何附加源的博客文章位于：
http://android.opensourceror.org/2010/01/18/android-source/
I had a problem like this a few weeks ago and it was due to ADT giving Eclipse some invalid information about where the Android sources are for the classpath. I fixed it by downloading the Android sources and attaching them myself. The bug is here:
http://code.google.com/p/android/issues/detail?id=7850
and a blog post on how to attach the sources is here:
http://android.opensourceror.org/2010/01/18/android-source/