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 49354 - Growing number of ClassPath instances - leak
Summary: Growing number of ClassPath instances - leak
Status: CLOSED FIXED
Alias: None
Product: java
Classification: Unclassified
Component: Classpath (show other bugs)
Version: 4.x
Hardware: PC All
: P2 blocker (vote)
Assignee: Tomas Zezula
URL:
Keywords: PERFORMANCE
: 49244 49258 (view as bug list)
Depends on:
Blocks: 49245
  Show dependency tree
 
Reported: 2004-09-21 13:47 UTC by Antonin Nebuzelsky
Modified: 2006-03-24 10:15 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
OptimizeIt screenshot (95.09 KB, image/png)
2004-09-21 13:49 UTC, Antonin Nebuzelsky
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Antonin Nebuzelsky 2004-09-21 13:47:31 UTC
Each invocation of JavaEditor.refreshAnnotations()
seems to generate new instances of
o.n.api.java.classpath.ClassPath which are hanging
around kept in memory via its SPIListener. See the
attached screenshot of OptimizeIt window. At the
bottom of the screenshot you can see the stack
trace where ClassPath instance is created. The
center of the screenshot shows the reference graph.
Comment 1 Antonin Nebuzelsky 2004-09-21 13:49:29 UTC
Created attachment 17789 [details]
OptimizeIt screenshot
Comment 2 Antonin Nebuzelsky 2004-09-23 17:00:33 UTC
*** Issue 49244 has been marked as a duplicate of this issue. ***
Comment 3 Antonin Nebuzelsky 2004-09-23 17:03:23 UTC
ClassPath instances can also be kept via SPIListener registered to
RefactoringClassPathImplementation (not only to
ProjectClassPathImplementation as shown in the attachment here). See
the issue 49244.
Comment 4 Antonin Nebuzelsky 2004-09-24 14:26:53 UTC
*** Issue 49258 has been marked as a duplicate of this issue. ***
Comment 5 Tomas Zezula 2004-09-29 08:58:54 UTC
Checking in
api/src/org/netbeans/modules/java/classpath/ProxyClassPathImplementation.java;
/cvs/java/api/src/org/netbeans/modules/java/classpath/ProxyClassPathImplementation.java,v
 <--  ProxyClassPathImplementation.java
new revision: 1.4; previous revision: 1.3
done
Comment 6 Antonin Nebuzelsky 2004-10-14 12:36:36 UTC
Partially fixed. The case with refreshAnnotations() is fixed now. But
the case with RefactoringClassPathImplementation as covered by issue
49258 still exists.
Comment 7 Tomas Zezula 2004-10-14 14:59:56 UTC
RefactoringClassPath fixed.

Checking in
src/org/netbeans/modules/refactoring/NbAbstractRefactoring.java;
/cvs/refactoring/src/org/netbeans/modules/refactoring/NbAbstractRefactoring.java,v
 <--  NbAbstractRefactoring.java
new revision: 1.10; previous revision: 1.9
done
Checking in
src/org/netbeans/modules/refactoring/RefactoringSupportImpl.java;
/cvs/refactoring/src/org/netbeans/modules/refactoring/RefactoringSupportImpl.java,v
 <--  RefactoringSupportImpl.java
new revision: 1.5; previous revision: 1.4
done
Processing log script arguments...
More commits to come...
Checking in
src/org/netbeans/modules/refactoring/classpath/RefactoringClassPathImplementation.java;
/cvs/refactoring/src/org/netbeans/modules/refactoring/classpath/RefactoringClassPathImplementation.java,v
 <--  RefactoringClassPathImplementation.java
new revision: 1.8; previous revision: 1.7
done
Processing log script arguments...
More commits to come...
Checking in src/org/netbeans/modules/refactoring/ui/RenameAction.java;
/cvs/refactoring/src/org/netbeans/modules/refactoring/ui/RenameAction.java,v
 <--  RenameAction.java
new revision: 1.19; previous revision: 1.18
done
Processing log script arguments...
More commits to come...
Checking in
test/qa-functional/src/org/netbeans/test/refactoring/Utility.java;
/cvs/refactoring/test/qa-functional/src/org/netbeans/test/refactoring/Utility.java,v
 <--  Utility.java
new revision: 1.11; previous revision: 1.10
done
Comment 8 Antonin Nebuzelsky 2004-10-14 17:05:13 UTC
Verified w/ build 20041014-1501.
Thanks!