Community
Participate
Working Groups
To reproduce this problem, enter the following code: public class Freeze { private Collection<Object> collection; public void method() { this.collection.stream().filter(value -> value != null); } } Then position the cursor at the start of the line containing the lambda expression, and press the key combination for Quick Fix. Eclipse will hang indefinitely, and must be killed. It might be related to bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=453523.
Which version of eclipse are you using, Tom? I can't reproduce this on master, so could be something about your set up or version of eclipse.
(In reply to Jayaprakash Arthanareeswaran from comment #1) > Which version of eclipse are you using, Tom? I can't reproduce this on > master, so could be something about your set up or version of eclipse. JDT 3.10.1.v20141112-0800
Tom, we fixed few bugs in this area and I believe this one has been fixed. Can you please try out a latest Mars build and see if it works for you as well. Thanks!
I'm afraid I can't reproduce it anymore with my existing Eclipse Luna, too. Code completion is no longer unresponsive, but it now gives an error message saying that code completion took too long to complete. So although code completion does not work for me in this situation, it does not result in an unresponsive Eclipse anymore, which still disappointing but acceptable.
(In reply to Tom van den Berge from comment #0) > It might be related to bug > https://bugs.eclipse.org/bugs/show_bug.cgi?id=453523. (In reply to Tom van den Berge from comment #4) > I'm afraid I can't reproduce it anymore with my existing Eclipse Luna, too. > Code completion is no longer unresponsive, but it now gives an error message > saying that code completion took too long to complete. The other bug you mentioned has the same symptoms. Will need to see if they are same. But with your code, though, I don't see any issues.
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.
