This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
I was running a Java program that was taking too long, and so I opened the Execution Window and right-clicked it and chose Terminate Process. The attached was thrown.
Created attachment 12670 [details] Stack trace
changing owner dkonecny -> pnejedly
It seems to me that there was one more kill than necessary, probably when the app was already about to finish.
*** Issue 38595 has been marked as a duplicate of this issue. ***
*** Issue 40199 has been marked as a duplicate of this issue. ***
OK, my previous evaluation was wrong, it looks more like if the AWT thread tries to kill itself. I've not reproduced it myself, but I'll prepare debugging patch so we can find the root cause.
Possibly related: I filed another issue similar to this. The running application had to have *two* JFrames open to reproduce it (I think both frames should try to kill the app on close, but I don't remember the details).
> AWT thread tries to kill itself Wrong again. The stack trace in ThreadDeath comes from the thread that performed the Thread.stop() (AWT in this case) and is completly unrelated to current stack of the thread being killed. The thread was already about to exit (external process already finished, RunClassThread got notified of the event and was just removing the process node from the process view) when you invoked the Terminate action.
It would probably help if we kill each thread of the execution thread grup separately instead of killing whole thread group at once. That way, we could prevent killing our own code in case the executed task was already finishing.
May be obsolete; I have not seen this when using Build -> Stop Building.
*** Issue 83294 has been marked as a duplicate of this issue. ***
It is still happening, at least in 5.5 it seems.
I would close as WONTFIX since I would like to remove the Processes node anyway.
*** Issue 82827 has been marked as a duplicate of this issue. ***
No Processes node now.