Bug 526511 - Content assist causes hang when using switch inside lambda
Summary: Content assist causes hang when using switch inside lambda
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.7.1a   Edit
Hardware: PC Linux
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact: Srikanth Sankaran CLA
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-26 10:00 EDT by Jakob van Kruijssen CLA
Modified: 2023-06-05 05:32 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jakob van Kruijssen CLA 2017-10-26 10:00:28 EDT 
In the following code:

public class EclipseBug {
    private enum Foo {
        FOO, BAR;
    }

    private void foo() {
        Arrays.asList(Foo.FOO, Foo.BAR).forEach(e -> {
            switch (e) {

            }
        });
    }
}

positioning the cursor inside the switch block and pressing ctrl+space will cause the IDE to hang (indefinitely, I think...)
Comment 1 Bram Klein Gunnewiek CLA 2017-11-06 05:47:41 EST 
Same issue here, as soon as I make a switch statement inside a foreach lambda the IDE hangs.
Comment 2 Eclipse Genie CLA 2020-06-28 15:40:04 EDT 
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.
Comment 3 Eclipse Genie CLA 2022-07-06 05:41:00 EDT 
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.
Comment 4 Srikanth Sankaran CLA 2023-06-05 05:32:02 EDT 
Not reproducible on master ...