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 61849 - Profiled app fails to terminate/close open JARs in classpath
Summary: Profiled app fails to terminate/close open JARs in classpath
Status: CLOSED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 4.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-05 11:41 UTC by gjkrupa
Modified: 2007-02-20 18:08 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description gjkrupa 2005-08-05 11:41:53 UTC
java version "1.5.0_04"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05)
Java HotSpot(TM) Client VM (build 1.5.0_04-b05, mixed mode, sharing)

Netbeans Profiler 4.1 Milestone 7

After running a profiled application that terminates with System.exit (scoped
performance analysis), JAR files on the classpath appear to be still opened by
the IDE, preventing them from being deleted due to sharing violations.  No
running processes are listed in the Runtime tab and Process Explorer (a tool
from www.sysinternals.com) shows only one Java.exe process running with tha JAR
files open.

This bug prevents the user from performing a 'clean'/'clean and build' on the
project (and any projects that also have JARs in the application's classpath). 
So far the only way to fix this that I have found is to terminate and restart
the IDE.
Comment 1 iformanek 2005-10-21 13:19:07 UTC
This is indeed the case for all JAR files on the classpath, regardless of the 
application behavior (i.e. does not have to exit via System.exit).

Fixed in M10, thanks for reporting this!
Comment 2 ehucka 2006-10-09 12:11:29 UTC
Verification of old issues.
Comment 3 Alexander Kouznetsov 2007-02-20 10:19:04 UTC
Closing old issues
Comment 4 Alexander Kouznetsov 2007-02-20 18:08:40 UTC
Reverting to original Target Milestone value changed by mistake. Sorry for
inconvenience.