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.

Bug 38320

Summary: Exception dialog when stopping an external Java process
Product: platform Reporter: Jesse Glick <jglick>
Component: ExecutionAssignee: Petr Nejedly <pnejedly>
Status: RESOLVED WONTFIX    
Severity: blocker CC: isullivan, tboudreau
Priority: P3    
Version: 3.x   
Hardware: PC   
OS: Linux   
Issue Type: DEFECT Exception Reporter:
Bug Depends on: 83313    
Bug Blocks:    
Attachments: Stack trace

Description Jesse Glick 2003-12-24 19:12:50 UTC 
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.
Comment 1 Jesse Glick 2003-12-24 19:14:59 UTC 
Created attachment 12670 [details]
Stack trace
Comment 2 Marian Mirilovic 2004-01-14 15:24:31 UTC 
changing owner dkonecny -> pnejedly
Comment 3 Petr Nejedly 2004-02-17 13:03:19 UTC 
It seems to me that there was one more kill than necessary, probably
when the app was already about to finish.
Comment 4 Petr Nejedly 2004-02-17 13:05:50 UTC 
*** Issue 38595 has been marked as a duplicate of this issue. ***
Comment 5 Petr Nejedly 2004-02-18 12:04:53 UTC 
*** Issue 40199 has been marked as a duplicate of this issue. ***
Comment 6 Petr Nejedly 2004-02-18 12:08:14 UTC 
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.
Comment 7 _ tboudreau 2004-02-18 12:26:17 UTC 
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).
Comment 8 Petr Nejedly 2004-10-12 10:21:14 UTC 
> 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.
Comment 9 Petr Nejedly 2005-03-03 13:17:11 UTC 
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.
Comment 10 Jesse Glick 2005-04-05 23:10:26 UTC 
May be obsolete; I have not seen this when using Build -> Stop Building.
Comment 11 Petr Nejedly 2006-08-23 18:29:36 UTC 
*** Issue 83294 has been marked as a duplicate of this issue. ***
Comment 12 Petr Nejedly 2006-08-23 18:30:31 UTC 
It is still happening, at least in 5.5 it seems.
Comment 13 Jesse Glick 2006-08-23 18:39:05 UTC 
I would close as WONTFIX since I would like to remove the Processes node anyway.
Comment 14 Petr Nejedly 2006-08-28 10:17:15 UTC 
*** Issue 82827 has been marked as a duplicate of this issue. ***
Comment 15 Jesse Glick 2006-10-23 23:34:37 UTC 
No Processes node now.