Community
Participate
Working Groups
I20040219 After doing development in my workspace for awhile, doing simple coding and debugging, I invoked code asist. It took over twenty seconds for it to respond, during which time the UI was dead. While I was waiting, I went to the console and obtained a stack dump, which i will attach. It appears to be opening zip files and searching for sources, just so it can show parameter name hints. If it does this at all, it should really be doing it in the background to make code assist responsive.
Created attachment 8021 [details] Stack trace during code assist
Any steps to reproduce ? You must have been GC'ing or swapping...
To be more precise, the delay occurred after selecting a completion, but before the completion actually got applied in the editor. I can't remember what I was completing on - possibly I hit a class that I had not completed on yet during that session, so it had to populate some caches? Also note that I work with almost all plugins as external, with only a few core plugins in my workspace as source.
Feels like a UI issue. I heard rumors about this occurring in similar conditions. FYI: JDT Core sometimes perform a quick search to find type names, but if you got completion proposals, our job was finished. Moving to JDT/UI.
The stacktrace shows that there is already a proposal selected and we're guessing arguments. Can you disable the argument guessing (Java > Editor > Code Assist > Guess filles argument names) and see if that makes a difference? If you're really sure that this ahppend before applying a proposal, can you get a stacktrace again? In that case it would definitly be jdt.core.
As I said in comment #3, I believe I had selected a proposal, hit enter to perform the completion, and then in froze. Unfortunately I don't remember now exactly what I was completing on, and I can't reproduce it.
Philippe, do you have some hints why you feel it's a UI problem? The stack trace shows that this is in the second code assist, performed to evaluate argument proposals.
I remember some GC'ing issues Erich mentionned causing pauses after completion. There could be something wrong in our land when binding parameter names though, ... but without any steps it is hard to guess.
>I remember some GC'ing issues Erich mentionned causing pauses >after completion. this problem was fixed before M7, so this cannot be the culprit
Moving to JDT/Core since it seems to be spending time reading parameter names from attached source. Would still need steps to reproduce.
I have no test case and i can not reproduce the problem. Closed.
