Community
Participate
Working Groups
I have relatively big project in Eclipse ~ 330Mb of sources, several source folders are configured as well as number of jars imported. With "Guess filled argument names" feature turned on and code assist hangs up IDE for few minutes before it can guess argument names for some arguments or sometimes it offers me only "null"s as arguments. I noticed that this usually occurs more often when at least one of argument types is generic enough like java.lang.Object or java.lang.String But the thing is that there are not too much variables/members directly visible in code assist context - may be it's trying to discover indirect matches as well as other visible entities (like static members)??? But anyway, the resulting list of proposals is never than 2-3 elements after 5 minutes of waiting... Should I disable this very handy feature - the IDE works fast enough. P.S.: Version: 3.1.0 Build id: I20050401-1645
May you have a try with last integration build and let us know if this still happens? We worked all April month to increase performances in all JDT/Core areas. We've made tests on "Monster" workspace and does no longer notice seach performance issue for code assist. If you still get it, please provide a precise test case to help us to figure out what happens here, thanks
This bug look like a duplicate of bug 86579. Reopen this bug if you can reproduce the problem with latest integration build. *** This bug has been marked as a duplicate of 86579 ***
