Community
Participate
Working Groups
Created attachment 262643 [details] A visual example of the bug The bug: When using the recommendations window that normally appear when pressing the ctrl + space shortcut, if you remove a comment (using backspace) the recommendations window starts to show duplicates of every recommendation. Both the single-line (//) and multi-line (/**/) comments are affected. Speculation: The number of slashes does not seem to affect the outcome nor type of comment, which leads me to believe the bug only appears when the recommendations windows is open and you are moving from a comment to normal code without closing the window. How to replicate: 1. Type "//" in a normal code setting 2. Open the recommendations window (ctrl + space is default) 3. Press backspace twice to remove the comment while the window is still open
(In reply to Julius Hager from comment #0) > How to replicate: > > 1. Type "//" in a normal code setting > > 2. Open the recommendations window (ctrl + space is default) > > 3. Press backspace twice to remove the comment while the window is still open Thank you so much for the detailed bug report! This is much appreciated. I can reproduce the behavior you describe both with Code Recommenders enabled and without, so this seems to be a general issue with the way JDT handles proposal computers when the cursor switches document partitions (from comment to non-comment). @JDT team: I have reproduced this with a plain Eclipse 4.6 SDK from [1]. The only difference to the reporter's screenshot is that proposals are only duplicated, not quadruplicated (is this a word?), as less proposal computers are active. [1] <http://download.eclipse.org/eclipse/downloads/drops4/R-4.6-201606061100/>
This is visible after the fix for bug 406463.
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. 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. -- The automated Eclipse Genie.
Still reproducible.