Eclipse Community Forums: Java Development Tools (JDT) » Content Assist [Intellisense] Sending Machine to 100% CPU

Home » Language IDEs » Java Development Tools (JDT) » Content Assist [Intellisense] Sending Machine to 100% CPU(When doing smart lookup for api, Eclipse goes to 100% CPU)

Content Assist [Intellisense] Sending Machine to 100% CPU [message #658151]

Mon, 07 March 2011 02:17

Eclipse User

I'm using Eclipse for an Android tutorial.

The problem is every time I type in some code and hit the period for a method, my machine cranks up to 100% CPU, and the fan starts huffing and puffing like it's climbing K2. It can take several minutes for it to calm back down again.

It makes it impossible to type code into the editor. I will tell you this though -- I wonder if its network related since it performs better during the day time than at night...

But why does doing Intellisense look up require so much computing power?!

[Updated on: Tue, 08 March 2011 15:42] by Moderator

Re: Intellisense Sending Machine to 100% CPU [message #658201 is a reply to message #658151]

Mon, 07 March 2011 06:53

Eclipse User

Check if you accidentally added a non jar file to your class path. Some version back they changed the jar selection dialog to show all files instead of just jars and the content assist chokes because it tries to parse them anyway.

Re: Intellisense Sending Machine to 100% CPU [message #658526 is a reply to message #658201]

Tue, 08 March 2011 15:21

Eclipse User

This is currently all standard Android development, so the project was built by the template that Google supplies.

All I have done is modify one class and added or modified three standard xml files.

I checked the build path in Eclipse and the only thing listed is the Android 2.2 jar file.

Re: Content Assisst Sending Machine to 100% CPU [message #658527 is a reply to message #658526]

Tue, 08 March 2011 15:27

Eclipse User

Looks like I found my answer in another thread.

I was calling it "Intellisense" but it's actually "Content Assist" for Eclipse.

There is a known bug with Helios and Ecilpse.

We are advised to use 3.5 or less for the Android plug in.

http://developer.android.com/sdk/eclipse-adt.html

Since I'm already on 3.6, I decided to try and turn off Content Assist using this article:

http://stackoverflow.com/questions/4906137/disable-content-a ssist-in-eclipse

[Updated on: Tue, 08 March 2011 15:30] by Moderator

Re: Content Assisst Sending Machine to 100% CPU [message #658529 is a reply to message #658527]

Tue, 08 March 2011 15:42

Eclipse User

So, the most refined way to "fix" this issue for now if you are using

Eclipse 3.6 (Helios)
Android SDK

Is to configure Content Assist by deselecting Auto-Activation.

You can leave all the other settings alone.

If you want automatic Content Assist, then set the delay to a much higher number, than the default 200ms. I find that 2000ms seems to work.

Previous Topic:	Re: Debug : Step Over doesn't work
Next Topic:	Using AST to parse my code with eclipse 3.2

Goto Forum:

-=] Back to Top [=-

Current Time: Tue Jul 01 14:54:33 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter