Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 542574

Summary: Infinite Loop in CompletionParser.resumeOnSyntaxError
Product: [Eclipse Project] JDT Reporter: Ian Robertson <ianbrobertson>
Component: CoreAssignee: Stephan Herrmann <stephan.herrmann>
Status: CLOSED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: ianbrobertson, jarthana, stephan.herrmann
Version: 4.8   
Target Milestone: 4.20   
Hardware: PC   
OS: Linux   
See Also: https://bugs.eclipse.org/bugs/show_bug.cgi?id=482663
Whiteboard: stalebug
Attachments:
Description Flags
ParserInfiniteLoop.java - triggers bug none

Description Ian Robertson CLA 2018-12-09 16:12:44 EST
Created attachment 276871 [details]
ParserInfiniteLoop.java - triggers bug

When editing the attached file, if I place the cursor on line 7 between "entry" and ")", and pressing the "." key, the eclipse UI immediately becomes non-responsive, and appears to do so until eclipse is killed.

Using jstack to grab stack traces, the traces for thread "main" vary, but all include

	at org.eclipse.jdt.internal.codeassist.complete.CompletionParser.resumeOnSyntaxError(CompletionParser.java:5519)

This may or may not be related to #482663.
Comment 1 Jay Arthanareeswaran CLA 2018-12-10 05:36:46 EST
(In reply to Ian Robertson from comment #0)
> This may or may not be related to #482663.

Looks so. I see that Eclipse no longer hangs when assist is invoked. It does't offer any suggestions, but that'll be a different topic.
Comment 2 Eclipse Genie CLA 2020-12-04 20:26:41 EST
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 2023-01-30 13:21:45 EST
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 Stephan Herrmann CLA 2023-01-30 16:22:58 EST
I can no longer reproduce in 2022-06 (4.25)

I'll take an informed guess that this was fixed via 539685

*** This bug has been marked as a duplicate of bug 539685 ***