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 131618 [details] Dump file. To reproduce: - start IDE with empty userdir - create new Java project - wait until scanning finishes - type "111" at the very beginning of JavaApplication1.java http://beetle.cz.oracle.com/data/transfer/jskrivanek/heapdump.hprof Product Version: NetBeans IDE Dev (Build 201302192300) Java: 1.7.0_15; Java HotSpot(TM) 64-Bit Server VM 23.7-b01 Runtime: Java(TM) SE Runtime Environment 1.7.0_15-b02 System: Windows 7 version 6.1 running on amd64; Cp1250; en_US (nb)
On the technical level, this fixes the bug: http://hg.netbeans.org/main/nb-javac/rev/1f9c3e45acfc http://hg.netbeans.org/jet-main/rev/aa0993ce37c6 Its however unclear under which component this bug belongs. As the fix (and bug) is in the nb-javac, it should belong to a component where our dashboard counts the nb-javac's source lines. But that appears to be neither java/source nor java/compiler. So reassigning to ide/code to pass to the component under which this code belongs (i.e. under which these lines of code are counted in the dashboard).
Source line counter should since now count also nb-javac code. (It will appear in dashboard once we assign component/subcomponent to nb-javac). Will it be java/compiler, or we want to create brand new component?
(In reply to comment #2) > Source line counter should since now count also nb-javac code. (It will appear Thank you. > in dashboard once we assign component/subcomponent to nb-javac). Will it be > java/compiler, or we want to create brand new component? java/compiler is the correct component for that.
...and since today, java/compiler is live on dashboard. Passing to java/complier, and marking as fixed according to comment #1.
(In reply to comment #4) > ...and since today, java/compiler is live on dashboard. Passing to > java/complier, and marking as fixed according to comment #1. Thanks!