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 128661 - memory leak in org.netbeans.modules.gsfpath.api.classpath.GlobalPathRegistry
Summary: memory leak in org.netbeans.modules.gsfpath.api.classpath.GlobalPathRegistry
Status: RESOLVED FIXED
Alias: None
Product: editor
Classification: Unclassified
Component: CSL (API & infrastructure) (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Torbjorn Norbye
URL:
Keywords: PERFORMANCE
Depends on:
Blocks: 70052 99077
  Show dependency tree
 
Reported: 2008-02-28 08:07 UTC by Tomas Mysik
Modified: 2009-02-19 20:45 UTC (History)
2 users (show)

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 Tomas Mysik 2008-02-28 08:07:51 UTC
Sorry, I'm not able to find GSF component.

Try to run WebProjectTest.testWebProjectIsGCed() (it's disabled now), WebProject cannot be GCed. See issue #99077:

private static org.netbeans.modules.gsfpath.api.classpath.GlobalPathRegistry 
org.netbeans.modules.gsfpath.api.classpath.GlobalPathRegistry.DEFAULT->
org.netbeans.modules.gsfpath.api.classpath.GlobalPathRegistry@1b07961-paths->
java.util.HashMap@2fab89-table->
[Ljava.util.HashMap$Entry;@1d93fe7-[13]->
java.util.HashMap$Entry@b2b928-value->
java.util.ArrayList@2f8262-elementData->
[Ljava.lang.Object;@7b6097-[0]->
org.netbeans.modules.gsfpath.api.classpath.ClassPath@e0ce0f-impl->
org.netbeans.modules.web.project.GsfBootClassPathImplementation@322f85-evaluator->
org.netbeans.spi.project.support.ant.PropertyUtils$SequentialPropertyEvaluator@beb1c4-listeners->
java.util.ArrayList@1c6ac9-elementData->
[Ljava.lang.Object;@e8dfb1-[3]->
org.netbeans.modules.web.project.ProjectWebModule@15419bb-project->
org.netbeans.modules.web.project.WebProject@1bbdd48)
Comment 1 Torbjorn Norbye 2008-03-10 20:59:39 UTC
Fixed in changeset 11da145c60f1.

I also verified that the test failed before and succeeds now.  I didn't reenable it because the test puts up an
interactive dialog (something about no server being configured) so I didn't want to possibly break commit validation by
enabling it, but at least I believe this leak will no longer affect the test.
Comment 2 Tomas Mysik 2008-03-11 11:00:49 UTC
I will look at it. Thanks.
Comment 3 Martin Krauskopf 2009-02-02 14:37:16 UTC
'ruby/gsf -> editor/csl' mass-move to be able to deleted gsf/ruby. Having to
change the version and platform of all closed moved issues to the same due to
Issuezilla deficiencies - choosing version == 6.5 and TM = 7.0.