Bug 544673 - DebugException: Terminate failed
Summary: DebugException: Terminate failed
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.10   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2019-02-21 09:47 EST by Patrick Tasse CLA
Modified: 2023-03-25 12:31 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Patrick Tasse CLA 2019-02-21 09:47:07 EST
This started happening very frequently when I use the Terminate button to kill a debug session on an Eclipse Application or JUnit Plug-In Test.

org.eclipse.debug.core.DebugException: Terminate failed
	at org.eclipse.debug.core.model.RuntimeProcess.terminate(RuntimeProcess.java:230)
	at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.terminate(JDIDebugTarget.java:1774)
	at org.eclipse.jdt.internal.debug.core.model.JDIDebugTarget.shutdown(JDIDebugTarget.java:1966)
	at org.eclipse.jdt.internal.debug.core.JDIDebugPlugin.stop(JDIDebugPlugin.java:368)
	at org.eclipse.osgi.internal.framework.BundleContextImpl$4.run(BundleContextImpl.java:838)
	at org.eclipse.osgi.internal.framework.BundleContextImpl$4.run(BundleContextImpl.java:1)
	at java.security.AccessController.doPrivileged(Native Method)
	at org.eclipse.osgi.internal.framework.BundleContextImpl.stop(BundleContextImpl.java:831)
	at org.eclipse.osgi.internal.framework.EquinoxBundle.stopWorker0(EquinoxBundle.java:1019)
	at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.stopWorker(EquinoxBundle.java:362)
	at org.eclipse.osgi.container.Module.doStop(Module.java:643)
	at org.eclipse.osgi.container.Module.stop(Module.java:505)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.decStartLevel(ModuleContainer.java:1824)
	at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1743)
	at org.eclipse.osgi.container.SystemModule.stopWorker(SystemModule.java:275)
	at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule.stopWorker(EquinoxBundle.java:195)
	at org.eclipse.osgi.container.Module.doStop(Module.java:643)
	at org.eclipse.osgi.container.Module.stop(Module.java:505)
	at org.eclipse.osgi.container.SystemModule.stop(SystemModule.java:207)
	at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule$1.run(EquinoxBundle.java:213)
	at java.lang.Thread.run(Thread.java:748)

eclipse.buildId=4.10.0.I20181206-0815
java.version=1.8.0_171
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments:  -product org.eclipse.epp.package.committers.product
Command-line arguments:  -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.committers.product
Comment 1 Sarika Sinha CLA 2019-02-21 23:45:15 EST
Does it terminate with this exception or doesn't terminate?
Comment 2 Andrey Loskutov CLA 2019-02-24 03:38:13 EST
Please provide steps to reproduce, your exact Eclipse version and explain what exactly is not working.
Comment 3 Patrick Tasse CLA 2019-03-26 09:26:57 EDT
Sorry for not responding earlier.

The issue with Terminate failed started occurring frequently a few months ago. When I noticed the Error log entry mentioned above, I thought it was directly related, so I wrote the bug.

But now I have noticed that, while the Terminate failed issue still occurs, it does not log this in the Error log when it happens.

I have since updated to 2019-03 and I still have the occasional Terminate failed. After the pop-up error dialog, the Debug view shows the process as terminated, but the application is still running and must be killed from the OS.

My current setup is:

eclipse.buildId=4.11.0.I20190307-0500
java.version=1.8.0_171
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments:  -product org.eclipse.epp.package.committers.product
Command-line arguments:  -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.committers.product
Comment 4 Sarika Sinha CLA 2019-03-26 22:37:32 EDT
Next time, can you watch out for the Details shown on "Details" button click from the Pop up dialog ?

And what kind of program are you trying to terminate?
How does Debug view look before terminate action ?
Comment 5 Patrick Tasse CLA 2019-03-28 12:02:40 EDT
Not sure if this is all directly related but...

I just had a "Terminate failed" dialog, after doing File -> Restart on a launched Eclipse application. The dialog does not have a Details button.

The application was closed. The Debug view shows the process <terminated>.

In the Console I see the following in red:

pure virtual method called
terminate called without an active exception

And I had a "Ubuntu has crashed" popup with details that seemed to show Java had crashed.
Comment 6 Sarika Sinha CLA 2019-03-29 01:08:56 EDT
I could find these JDK bugs -
https://bugs.openjdk.java.net/browse/JDK-8146009
https://bugs.openjdk.java.net/browse/JDK-8169634
Comment 7 Eclipse Genie CLA 2021-03-19 13:41:27 EDT
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 8 Eclipse Genie CLA 2023-03-25 12:31:40 EDT
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.