René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Stop with integratedTerminal/externalTerminal still uses vm.exit(0), shutdown hooks do not run","articleBody":"Follow-up to #1720 (fixed by microsoft/java-debug#645).\n\nSince 0.60.2026102705, the first **Stop** sends `terminate`, keeps JDI attached, and the JVM shuts down gracefully, so breakpoints in shutdown hooks are hit. This works with `\"console\": \"internalConsole\"`. With `\"console\": \"integratedTerminal\"` or `\"externalTerminal\"` the problem from #1720 is still there: shutdown hooks do not run at all.\n\n##### Environment\n- Operating System: Linux Mint 22.1\n- JDK version: 21.0.7\n- Java Debugger extension version: 0.60.2026102705 or later\n\n##### Steps To Reproduce\n1. Use the program from #1720:\n   ```java\n   public class App {\n       public static void main(String[] args) throws Exception {\n           Runtime.getRuntime().addShutdownHook(new Thread(() -> {\n               System.out.println(\"hook start\");   // breakpoint here\n               System.out.println(\"hook end\");\n           }));\n           Thread.sleep(Long.MAX_VALUE);\n       }\n   }\n   ```\n2. Launch it with `\"console\": \"integratedTerminal\"` (or `\"externalTerminal\"`).\n3. Set a breakpoint on the `hook start` line.\n4. Press **Stop**.\n\n##### Current Result\nThe JVM is killed: the breakpoint is not hit and `hook start` is not printed in the terminal.\n\n##### Expected Result\nThe same as with `internalConsole`: the JVM gets SIGTERM, the debugger stays attached, the shutdown-hook breakpoint is hit, and the session ends when the JVM exits.\n\n##### Additional Informations\n`TerminateRequestHandler` calls `debugSession.terminate()`, and [`DebugSession.terminate()`](https://github.com/microsoft/java-debug/blob/main/com.microsoft.java.debug.core/src/main/java/com/microsoft/java/debug/core/DebugSession.java) does:\n\n```java\nif (vm.process() != null && vm.process().isAlive()) {\n    vm.process().destroy();\n} else if (vm.process() == null || vm.process().isAlive()) {\n    vm.exit(0);\n}\n```\n\nIn terminal mode the debuggee is started through `runInTerminal` and connects to a `ListeningConnector`, so `vm.process()` is `null` and the code falls back to `vm.exit(0)`. JDWP `VirtualMachine.Exit` ends the JVM without running shutdown hooks.\n\n`DebuggeeProcessHelper.terminate()` can already destroy the process by `context.getProcessId()`, but it is only used when there is no debug session (`noDebug`). Even there it does not point to the JVM: VS Code's `runInTerminal` response gives the PID of the terminal shell, not of the debuggee.\n","author":{"url":"https://github.com/danilaslynko","@type":"Person","name":"danilaslynko"},"datePublished":"2026-11-12T21:13:50Z","url":"https://github.com/microsoft/vscode-java-debug/issues/1732"}