VM crashes if the debugger is suspended for too long
Answered
I am running a java web server app. I setup a few breakpoints, and they hit. However, if I leave the application suspended too long, the application server VM quits, and the console has this message:
Process finished with exit code 134 (interrupted by signal 6:SIGABRT)
I just started using Idea (from Eclipse), so I might be doing something wrong. Is there a timeout setting that I need to increase? I do not experience this when debugging the same application in Eclipse.
Idea info:
IntelliJ IDEA 2024.2.3 (Community Edition)
Build #IC-242.23339.11, built on September 25, 2024
Runtime version: 21.0.4+13-b509.17 aarch64 (JCEF 122.1.9)
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Please sign in to leave a comment.
If you are using remote debug, please see https://intellij-support.jetbrains.com/hc/en-us/community/posts/115000231084--IntelliJ-How-to-set-the-connect-timeout-values-when-remote-debugging.
I'm not remote debugging as far as I know. I just clicked the debug button for the configuration that I setup.
I think I found out why this is happening. For some reason, when I set a breakpoint Idea thinks that I want to suspend All threads, not just the executing thread. I am not sure why this is the default. Is there a setting to make this not the default when I create a breakpoint? That seems like the wrong default.