Eclipse Android SDK slow Content Assist performance

Question

Im running eclipse on my windows 7 machine, 64bit with 6gb ram and core 2 duo. Im currently running Eclipse 3.6 and android 2.2 SDK Im running jdk 1.6

Im noticing that when coding and the context popups to list methods of a class, it hangs Eclipse for up to 15 seconds. This is very frustrating.

One thing to note, when Eclipse hangs, my processor is maxed out, and is being worked by a java process. So its doing something whatever it is. But frequently everytime I finish an object with a period and the context box pops up, its becoming too painful to work with.

I changed some settings in the Eclipse.ini file such as: -Xms1024m -Xmx1024m --launcher.XXMaxPermSize 512m

Is there anything else I should look at:

Answer 1

After a google search

I have been able to find the bug report from Eclipse.

In short:

• It is a problem that arises when using Helios with ADT. As the ADT page on android.com says:

Caution: There are known issues with the ADT plugin running with Eclipse 3.6. Please stay on 3.5 until further notice.

• To fix it, you will have to use Eclipse 3.5 and put your project in a newly created workspace. (If you keep the workspace from Eclipse 3.6, the problem will occur even on Eclipse 3.5.)

Answer 2

A Work-around procedure is presented in comment#8 at this URL: http://code.google.com/p/android/issues/detail?id=7850

Example:

I'm coding against Froyo, and my target SdkVersion is 7 (AndroidManifest.xml). So for step 1, I downloaded this file:

https://android.googlesource.com/platform/frameworks/base/+archive/froyo-release.tar.gz

And then for step 2, I extracted the base/ directory of that .tgz file into my SDK path, which I install under /opt/android-sdk-linux_x86/. So here's the command I executed against the tgz to put everything where it goes:

tar -vzxf base-froyo.tar.gz -C /opt/android-sdk-linux_x86/platforms/android-7/sources/ base/

The end goal appears to be to place the actual sources into the "sources" folder in the SDK tree, so that when the auto-correct goes out looking for them, they are there.

snpe60 describes it more clearly:

Comment 7 by snpe60, Oct 14, 2010 This issue is happen because the ADT classpath container have an invalid source attachment by default. It is fixed in https://review.source.android.com/16569. This change enables changing the ADT clasppath container's source attachment and disables setting invalid source attachment. Hoping it will be available in ADT 8.0.0.