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 46797 - [perf] index map is never cleared
Summary: [perf] index map is never cleared
Status: RESOLVED DUPLICATE of bug 46550
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 4.x
Hardware: PC All
: P3 blocker (vote)
Assignee: issues@java
URL:
Keywords: PERFORMANCE
Depends on:
Blocks:
 
Reported: 2004-07-30 16:00 UTC by Pavel Flaska
Modified: 2007-09-26 09:14 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 Pavel Flaska 2004-07-30 16:00:39 UTC
ClassIndex.codebaseIndexes map is not cleared. I
played a little bit with the IDE and experienced,
that method JMManager.disposeCodebase() is never
called. This method is only one which removes
elements from map (more precisely called static
method ClassIndex.removeIndex()). The caller of
disposeCodebase() method - cleanUpCodebases() - is
called, but I did not understood enough the logic
to fix it.
Comment 1 Pavel Flaska 2004-07-30 16:07:48 UTC
Steps to reproduce:
i) start IDE,
ii) open some project(s),
iii) close all projects,
iv) open another project(s),
v) again you can close projects.

Steps ii) to v) can be repeated.

The number of items in ClassIndex.codebaseIndexes is still growing. 
Comment 2 Martin Matula 2004-07-30 19:29:51 UTC
As I explained in issue 46550 we clean codebases only if there are no
references to the corresponding classpath elements. The fact that the
codebases are never cleaned means, there is a leak somewhere - some
objects still keep hardreferences to classpath elements even after the
project is closed.

*** This issue has been marked as a duplicate of 46550 ***
Comment 3 Quality Engineering 2007-09-20 11:55:55 UTC
Reorganization of java component