Community
Participate
Working Groups
When auto-completing a method invocation, e.g. "foo.ba" [CTRL-SPACE], it seems that after selecting the desired method (for example, "foo.bar(int[] numbers)"), and hitting ENTER, it can take an enormous amount of time for Eclipse to return control to the user. It would seem that once you've selected the method, Eclipse performs an exhaustive search of objects that could be inserted as parameters. Particularly when auto-completing inside anonymous inner classes, I've seen this take upwards of 5 minutes between teh time I hit ENTER and the time when it actually returns control. It seems that during this time, the exhaustive search thread behaves very badly - the UI will not repaint (at all) for the duration of the search. So, two suggestions: 1. The thread performing this "guess" needs to yield every now and then! 2. Allow the "guess" to be cancelled, either in the normal fashion (the cancel button at bottom right of the UI) or by hitting escape. Of course, in the absence of #1, since the thread is apparently hoarding the event dispatcher or something like that, this isn't of much value...
Do you still see the problem ?
David, Not sure - I disabled the preference long ago as a workaround. I will re-enable and give it a shot. I currently have access to a 3.1.2 stable and a 3.2 M5 release of eclipse (and M6 tomorrow) - is there a specific build in which I should try this?
It's better if you could try with 3.2M6 but 3.2M5 will be good also.
I've been using 3.2M6 for a week or so now with this option turned on, and I haven't to date encountered the problem. In fact, it seems blazingly fast now. It would be nice to know what (if anything) has changed, but it seems to be working fine now. I'll update this bug again if I run into the problem later, but seems ok...
We have done a lot of work to improve performance but as i don't reproduce your problem with an old build, i cannot be sure that our improvments solve your problem. As you don't see the problem with 3.2M6, i close this bug as WORKSFORME. But if the problem seems to reappear don't hesitate to reopen this bug. Thanks for your help.
