Eclipse Community Forums: Java Development Tools (JDT) » Eclipse content assist unbearably slow with Android SDK

Help

Home

Home » Language IDEs » Java Development Tools (JDT) » Eclipse content assist unbearably slow with Android SDK

Show: Today's Messages :: Show Polls :: Message Navigator

Eclipse content assist unbearably slow with Android SDK [message #551646]

Sun, 08 August 2010 20:25

Michael Moser

Messages: 914
Registered: July 2009

Senior Member

(I am not sure whether this is an Eclipse JDT or an Android SDK issue,
so I try here first - if there is a better place to post this question
please advise!)

I recently downloaded and installed the Android SDK into Eclipse
Helios and started programming for the Android platform. This works
very well and the environment is very nice, there is only one thing
that really drives me nuts and that is the incredibly slow content
assist behavior:

I.e. whenever one types some identifier and then a '.' then normally
eclipse offers a list of possible fields and method withing seconds.
And while one continues to type that list gets shorter and shorter due
to the filtering until normally just one single matching entry
remains.

When writing an Android app, however, once one hits the '.' key
Eclipse always goes dead for 5-20(!) seconds until it finally delivers
the list of possible completions. During that time all keystrokes
except the first are ignored and lost. Apparently digging out the
fields and methods of an Android class takes "forever" with the
Android SDK. I am not sure whether this is some Helios bug/oddity or
whether that's something on the SDK side, although I can't imagine
what the "Googlers" might possibly have done wrong here...

Any idea or suggestion? Has maybe someone else had similar experience
with the Android SDK and maybe found a solution?

These frequent pauses are so annoying and constantly interrupting my
workflow and are really killing all the fun...

Michael

Report message to a moderator

Re: Eclipse content assist unbearably slow with Android SDK [message #551666 is a reply to message #551646]

Mon, 09 August 2010 04:39

Walter Harley

Messages: 847
Registered: July 2009

Senior Member

"Michael Moser" <michael.moser@freesurf.ch> wrote in message
news:oq3u56t9efcfjchi53sp4vqr818lneb18f@4ax.com...
> (I am not sure whether this is an Eclipse JDT or an Android SDK issue,
> so I try here first - if there is a better place to post this question
> please advise!)
>
> I recently downloaded and installed the Android SDK into Eclipse
> Helios and started programming for the Android platform. This works
> very well and the environment is very nice, there is only one thing
> that really drives me nuts and that is the incredibly slow content
> assist behavior:
>
> I.e. whenever one types some identifier and then a '.' then normally
> eclipse offers a list of possible fields and method withing seconds.
> And while one continues to type that list gets shorter and shorter due
> to the filtering until normally just one single matching entry
> remains.
>
> When writing an Android app, however, once one hits the '.' key
> Eclipse always goes dead for 5-20(!) seconds until it finally delivers
> the list of possible completions. During that time all keystrokes
> except the first are ignored and lost. Apparently digging out the
> fields and methods of an Android class takes "forever" with the
> Android SDK. I am not sure whether this is some Helios bug/oddity or
> whether that's something on the SDK side, although I can't imagine
> what the "Googlers" might possibly have done wrong here...

Completions are contributed by plug-ins. There are a myriad of things that
the plug-in author might have done wrong, and there are also possible
configuration issues, for instance, if for some reason your machine thinks
it needs to go to the internet or to a distributed file system to access
some libraries on the build path.

The best way to get to the heart of what is going wrong in a perf problem is
to take some thread dumps and look for where Eclipse is spending its time.
There are details on taking thread dumps at
http://wiki.eclipse.org/index.php/How_to_report_a_deadlock .

Report message to a moderator

Previous Topic:	Eclipse 3.5sr1 is painfully slow
Next Topic:	galileo Hangs Creating New Class

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Tue Apr 16 21:39:00 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter