Community
Participate
Working Groups
I have a production Eclipse application that fails to receive mouse/keyboard input when using the Java JDK 8u152, or later. The Java JDK 8u151 works just fine though. I found a sample plugin app that I downloaded from the following Eclipse tutorial where was able to demonstrate switching between the JDKs using Eclipse 4.5.2. https://www.eclipse.org/articles/Article-RCP-3/tutorial3.html https://www.eclipse.org/articles/Article-RCP-3/part3.zip Steps to reproduce... - Download and import the project from https://www.eclipse.org/articles/Article-RCP-3/part3.zip - Download and configure Eclipse to use Java JDK 8u151 and any later version (I used 8u152) - Run the plugin app from Eclipse using JDK 8u151 and it will work fine. - Run the plugin app from Eclipse using JDK 8u152 and the app will fail to receive any mouse/keyboard input.
See also https://www.eclipse.org/forums/index.php?t=rview&goto=1780621#msg_1780621 And bug 526533 comment 4.
*** Bug 526533 has been marked as a duplicate of this bug. ***
This issue is not reproducible on Windows 7 with Java v1.8.151 or Java v1.8.161 using Eclipse 4.5 or Eclipse 4.8.
Eclipse 4.4 and 4.5 hangs when launched with jre version 8u161. I'm not able to reproduce the problem with 4.6 and newer versions. My Mac OS version is 10.12.
(In reply to keith knight from comment #0) What version of Mac OS are you using?
(In reply to Lakshmi Shanmugam from comment #5) > (In reply to keith knight from comment #0) > What version of Mac OS are you using? I'm running 10.13.3, but I was also running 10.13.2 when the problem first happened.
I wasn't very clear in the original comment, but the problem is occurring on macOS (several different versions) with all Java updates since 8u151 (8u152, 8u161 and 8u162) using a commercial Eclipse RCP application. The problem of losing mouse/keyboard input to the application began with Java 8u152 and the only solution has been to limit the JDK/JRE to 8u151, which is now becoming more impossible because of mandatory updates that patch critical vulnerabilities.
Keith, please check whether it works for you when using 4.6.3 (http://archive.eclipse.org/eclipse/downloads/drops4/R-4.6.3-201703010400/) or newer.
I'm unable to import the example project and run it in any version of Eclipse higher that 4.5. Is there a trick to reconfiguring the example project?
I was able to verify the same example code using Eclipse 4.6.3 with both JDKs (8u151 and 8u152) and I did not experience the same mouse/keyboard problems I have with previous versions.
The following community forum mentions the exact same problem using 4.6 too. https://www.eclipse.org/forums/index.php?t=rview&goto=1780621#msg_1780621
This is exactly the same problem I'm reporting. UI not responding and thread dump shows no evidence of deadlocks. https://bugs.java.com/bugdatabase/view_bug.do?bug_id=8190319
The problem has been fixed in 4.6 via Bug 477979. This was a problem with non-standard JVMs, but now happens with Java > JDK 8u152 as well.
Created attachment 272443 [details] Git patch for 4.5.2 branch I've attached the patch that can be applied on the 4.5 maintenance branch. The patch is quite straightforward and doesn't involve native changes.
Any chance you can publish the patched artifacts? Thanks a lot! :)
My team has a project that is currently stuck on Eclipse 4.4.* which has this same issue. Any chance this patch will work for that version as well? (I wish we could back-port and create a hotfix for that one too - see bug 526533)
(In reply to Shami Willms from comment #17) > My team has a project that is currently stuck on Eclipse 4.4.* which has > this same issue. Any chance this patch will work for that version as well? > (I wish we could back-port and create a hotfix for that one too - see bug > 526533) Yes, the same patch will apply to the R4_4_maintenance branch.
*** This bug has been marked as a duplicate of bug 477979 ***
*** Bug 531107 has been marked as a duplicate of this bug. ***
