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.
private static final java.util.Map org.netbeans.api.java.source.JavaSource.finishedRequests-> java.util.WeakHashMap@8dfbca-table-> [Ljava.util.WeakHashMap$Entry;@15eaed9-[12]-> java.util.WeakHashMap$Entry@1661165-value-> java.util.LinkedList@823357-header-> java.util.LinkedList$Entry@e46a6b-next-> java.util.LinkedList$Entry@191221e-element-> org.netbeans.api.java.source.JavaSource$Request@1591419-javaSource-> org.netbeans.api.java.source.JavaSource@176f740-classpathInfo-> org.netbeans.api.java.source.ClasspathInfo@1032074-srcClassPath-> org.netbeans.api.java.classpath.ClassPath@1dc3b5b-impl-> org.netbeans.modules.java.j2seproject.classpath.SourcePathImplementation@127c1ab-sourceRoots-> org.netbeans.modules.java.api.common.SourceRoots@16775da-helper-> org.netbeans.modules.java.api.common.ant.UpdateHelper@3d68be-updateProject-> org.netbeans.modules.java.j2seproject.UpdateProjectImpl@a8604d-project-> org.netbeans.modules.java.j2seproject.J2SEProject@1949c1e
I will look at it.
This memory leak is just about the last opened java file holding single project. Maybe not so important.
I know that in real use it may not be that important, but it is important to me, as I want to make commit validation failing as soon as there is a single leak anywhere. But you can do anything to make the leak disappear - feel free to open new Java file in the test, if that helps you.
Fixed in: 1f9c9de8099a