Community
Participate
Working Groups
Created attachment 276204 [details] popup Ran a build on a large number of projects containing build files. That produced a lot of errors in the log accompanied by popups. Got one of the error: !MESSAGE An internal error occurred during: "Match Job".^M !STACK 0^M java.lang.IncompatibleClassChangeError: org.eclipse.core.runtime.Platform^M at org.eclipse.ui.internal.console.ConsolePatternMatcher$MatchJob.run(ConsolePatternMatcher.java:69)^M at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)^M This error filled up the .metadata/.log The workbench looks hanged infinitely but it is finite. Just take a while affecting overall performance.
Related to Bug 492461 ?
There was a fix via Bug 451797 in 4.6.2 which looks related to hanging with large outputs in console. But , the error popup java.lang.IncompatibleClassChangeError: org.eclipse.core.runtime.Platform^M at org.eclipse.ui.internal.console.ConsolePatternMatcher$MatchJob.run(ConsolePatternMatcher.java:69)^M at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)^M Looks different and it can be caused by wrong set of libraries in the install.
Created attachment 276250 [details] jstack
(In reply to Sarika Sinha from comment #2) > There was a fix via Bug 451797 in 4.6.2 which looks related to hanging with > large outputs in console. Using Eclipse 4.6.3 I could reproduce a deadlock using the snippet in Bug 461797 / comment 28 in a Mac. Found one Java-level deadlock: ============================= "Worker-39": waiting to lock monitor 0x0000000102249d78 (object 0x00000007810c33b0, a java.lang.Object), which is held by "Worker-19" "Worker-19": waiting to lock monitor 0x00000001014023c8 (object 0x0000000798980170, a java.io.PrintStream), which is held by "Worker-36" "Worker-36": waiting to lock monitor 0x0000000102249d78 (object 0x00000007810c33b0, a java.lang.Object), which is held by "Worker-19" (complete jstack attached) But this issue seems different to my original issue.
This is totally different.
We don't have much information to proceed.
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.
