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.
Created attachment 106715 [details] Screenshot from profiler showing how is the ELWhereUsedQuery is held and how it holds the javac I have seen this first in bug #196181, but also seen it today in my development IDE. The ELWhereUsedQuery keeps an instance of CompilationInfo (org.netbeans.api.java.source), which in turns keeps a javac instance in memory. The retained size of such instance can be pretty big. Instances of CompilationInfo should not be kept outside the java.source's or parsing.api's Tasks. In my development IDE, I see more that 15 instances of javac held this way. Seems they are held through the open find usages results (IIRC I had more or less that number of FU results open at the time). My build is a custom build based on changeset id #4ed445552239.
fixed in web-main#8f08d13302b0
Integrated into 'main-golden', will be available in build *201103080000* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/8f08d13302b0 User: Marek Fukala <mfukala@netbeans.org> Log: #196306 - ELWhereUsedQuery retains javac instances