With the Analyser check for "type definitions and record component access" being enabled (see screenshot), in certain cases (particularly after a Java code import) Analyser may get trapped in an eternal loop if the analysed variable happens to name a Java object.
This would lock Structorizer altogether. It seems to be an unwanted side effect of an inconsistent implementation of #1112.
Structorizer may also get trapped via the Content Assist on editing an element with such a vulnerable content (at the very same positions, i.e., by appending a dot to a variable declared with a Java class as type, see e.g. the screenshot from #1129), no matter whether or not the mentioned Analyser check is enabled.
With the Analyser check for "type definitions and record component access" being enabled (see screenshot), in certain cases (particularly after a Java code import) Analyser may get trapped in an eternal loop if the analysed variable happens to name a Java object. This would lock Structorizer altogether. It seems to be an unwanted side effect of an inconsistent implementation of #1112.
Structorizer may also get trapped via the Content Assist on editing an element with such a vulnerable content (at the very same positions, i.e., by appending a dot to a variable declared with a Java class as type, see e.g. the screenshot from #1129), no matter whether or not the mentioned Analyser check is enabled.
So it is a serious bug.