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 14369 - Running class using F5 leaves stale java.exe processes in memory
Summary: Running class using F5 leaves stale java.exe processes in memory
Status: CLOSED WONTFIX
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: Other Windows ME/2000
: P3 blocker (vote)
Assignee: issues@debugger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-08-12 20:59 UTC by hlavac
Modified: 2001-08-13 10:21 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description hlavac 2001-08-12 20:59:04 UTC 
I've noticed that after some time spent working in netbeans, java.exe crashed at me at strange time when i was not doing anything.
I checked task manager and found some good 50 java.exe processes running in memory...
New java.exe appears each time i run something using F5.
I suspected they were debugging sessions, but quick check of debug window
showed that there were none. Looks like a bug in debug session cleanup to me...
This happens on Win2000 (SP2) and also on Win98 SE if i remember correctly.
I think when dialog pops up at me saying there is already a debug session and whether i should start a new one or replace existing session, I selected checkbox to not ask anymore and selected replace...

Netbeans version 3.2.1 RC2 (build 89) and also some older releases...
Comment 1 Tomas Hurka 2001-08-13 09:05:09 UTC 
It seems to me like debugger issue.
Comment 2 Jan Stola 2001-08-13 10:16:03 UTC 
It is a bug of JDK. Debugged processes are not destroyed when
debugging on Hotspot VM. See
http://developer.java.sun.com/developer/bugParade/bugs/4420844.html
Comment 3 Jan Stola 2001-08-13 10:21:48 UTC 
Wontfix -> Closed