Eclipse 3.6 frequently stalls during Content Assist

Question

The auto complete stalls so frequently and for so long, I quit using it altogether.

Answer 1

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. "

Answer 2

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.

Answer 3

For me the problem went away when I increased the memory for the vm. Put this in your eclipse.ini:

-Xms512m
-Xmx1024m