Community
Participate
Working Groups
Created attachment 270134 [details] Thread dump 1 Today Eclipse started using high CPU while working on an enum class that also used some Lambda's as parameters. Two threads seem to be looping (50% CPU use on a 4 core machine). This has been happening 30+ minutes already, I'll need to restart Eclipse to fix it. I made a few Jstack dumps, which I've attached. The culprit seem to be two RUNNABLE Threads: "Text Viewer Hover Presenter" and "Recommenders-Timeout-Manager".
Created attachment 270135 [details] Thread dump 2
Created attachment 270136 [details] Thread dump 3
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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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.
Yep, this code area: "Text Viewer Hover Presenter" #2552 daemon prio=1 os_prio=-2 tid=0x000000001ea41800 nid=0x1f00 runnable [0x000000007d11e000] java.lang.Thread.State: RUNNABLE at org.eclipse.jdt.internal.codeassist.impl.AssistParser.copyState(AssistParser.java:138) at org.eclipse.jdt.internal.codeassist.impl.AssistParser.fallBackToSpringForward(AssistParser.java:2205) at org.eclipse.jdt.internal.codeassist.impl.AssistParser.resumeAfterRecovery(AssistParser.java:2225) at org.eclipse.jdt.internal.codeassist.select.SelectionParser.resumeAfterRecovery(SelectionParser.java:1541) at org.eclipse.jdt.internal.compiler.parser.Parser.resumeOnSyntaxError(Parser.java:12971) is known to be incomplete / buggy concerning completion. Apparently, also selection is affected. It's all due to irregularities in the Java grammar, which need lots of workarounds to squeeze it into a grammar that the parser generator jikespg accepts. These workarounds then conflict with the highly sophisticated machinery of syntax recovery. We haven't yet found a strategy to improve the situation. We have open bugs concerning completion, which should be sufficient to remind us of the problem.
