Community
Participate
Working Groups
I am trying to use build I20041005 but have come to the conclusion that the build is unusable for me. The problem is that, every minute or so, Eclipse becomes unresponsive. I have taken several snapshots and have already logged bug 75646 against JDT UI. One of the blockages I experienced was due to code assist being blocked, most likely by a background job. Not sure if this is one of the causes or just a symptom but I'm marking it as critical since, as I said, I cannot work in todays itegration build. I will attach a VM trace.
Created attachment 15008 [details] VM trace of blocked code assist I should add that this is NOT a deadlock. The system did recover. However, it is not good to block the UI thread without some sort of user feedback.
*** This bug has been marked as a duplicate of 75646 ***
This is not a duplicate of 75646. I'll downgrade the severity but this is a separate issue. Code that is running in the UI thread should not block on locks without providing feedback of some sort to the user. One option I can think of in this case would be to show the content assist window with some indication that it is waiting to be populated. I, as the user, could then decide to wait or to continue typing.
The stack trace shows that quick fix/assist (Ctrl+1) has been used and not code assist (Ctrl+Space). Is this correct? Code assist does not need an AST to get its completions.
Probably. The key sequences have become second nature so it's hard to remember which I used.
The quick assist and codeassist UI is the same and is done by the editor. Collecting proposals in the background (= calling IContentAssistProcessor.computeCompletionProposals) should not be a problem for both of these features
Discussed with Martin: Quick Assist/Fix is more affected than Code Assist because other plug-ins can provide "bad" assists or fixes while code assist is under our fill control. Even without support from Platform Text Quick Assist/Fix infrastructure could limit how much time is allowed to retrieve assists and fixes from contributors. This should be done no matter whether Platform Text provides better support in this area.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it and remove the stalebug whiteboard tag. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. --
