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.
Build: NetBeans IDE 7.4 (Build 201310111528) VM: Java HotSpot(TM) Client VM, 24.72-b04, Java(TM) SE Runtime Environment, 1.7.0_72-b14 OS: Windows 7 User Comments: GUEST: Debugging and mostly it was scanning background or something like that jgawera: Netbeans struggling with out of memory errors Stacktrace: java.lang.OutOfMemoryError: Java heap space at com.sun.tools.javac.util.Position$LineMapImpl.build(Position.java:153) at com.sun.tools.javac.util.Position.makeLineMap(Position.java:77) at com.sun.tools.javac.parser.JavadocTokenizer.getLineMap(JavadocTokenizer.java:445) at com.sun.tools.javac.parser.Scanner.getLineMap(Scanner.java:127) at com.sun.tools.javac.parser.JavacParser.parseCompilationUnit(JavacParser.java:3182) at org.netbeans.lib.nbjavac.services.NBParserFactory$NBJavacParser.parseCompilationUnit(NBParserFactory.java:193)
Created attachment 151613 [details] stacktrace
As can be seen from the attached heapdump-762472, the most memory consuming objects (object with the biggest retain sizes originate in FormEditor. Reassigning.
The problem in the attached heapdump-762472 seems to be that com.fkilogistex.systems.wcsgui.screen.components.JDateChooser adds itself as a listener to javax.swing.MenuSelectionManager and never unregisters. There are hundreds JDateChooser$3 listeners - looks like during GUI editing many JDateChooser components got created, but they cannot be released. It is a huge memory leak, MenuSelectionManager holds these components for ever and through them also other parts of GUI builder are held. This is a problem of a custom component, we can't do anything with it.