Community
Participate
Working Groups
Hi, When we try to kill eclipse.exe from windows taskbar eclipse doesn't get killed. 1) Launch Eclipse IDE 2) Launch Task Manager 3) Kill Eclipse.exe process eclipse doesn't get killed. If we try to kill the java process that launched eclipse we get the following error- "Java was started but returned exit code=1" This occurs after JAVA 9. Could someone please share the reason/fix for the issue? Thanks
(In reply to Karthik Bhat from comment #0) > Hi, > When we try to kill eclipse.exe from windows taskbar eclipse doesn't get > killed. > 1) Launch Eclipse IDE > 2) Launch Task Manager > 3) Kill Eclipse.exe process eclipse doesn't get killed. Are you sure that the eclipse.exe (launcher) isn't killed but the Java process continues to run? > If we try to kill the java process that launched eclipse we get the > following error- > "Java was started but returned exit code=1" > > This occurs after JAVA 9. This works fine for me using the Process Explorer to kill it, but I'm on Windows 7. Niraj, please test on Windows 10.
(In reply to Dani Megert from comment #1) > (In reply to Karthik Bhat from comment #0) > > Hi, > > When we try to kill eclipse.exe from windows taskbar eclipse doesn't get > > killed. > > 1) Launch Eclipse IDE > > 2) Launch Task Manager > > 3) Kill Eclipse.exe process eclipse doesn't get killed. > > Are you sure that the eclipse.exe (launcher) isn't killed but the Java > process continues to run? > > > > If we try to kill the java process that launched eclipse we get the > > following error- > > "Java was started but returned exit code=1" > > > > This occurs after JAVA 9. > > This works fine for me using the Process Explorer to kill it, but I'm on > Windows 7. > > > Niraj, please test on Windows 10. Tested latest Eclipse 4.8 build on Windows10 version 1803: - I am able to kill(End Task) the eclipse.exe from the TaskManager - Also can close Eclipse from taskbar.
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.
