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 Dev (Build 201401100002) VM: Java HotSpot(TM) 64-Bit Server VM, 24.45-b06, Java(TM) SE Runtime Environment, 1.7.0_45-b08 OS: Windows 7 User Comments: mkhramov: Runned 3 junit tests simultaneously with lot of output from them Stacktrace: java.lang.OutOfMemoryError: Java heap space at java.lang.StringCoding$StringDecoder.decode(StringCoding.java:149) at java.lang.StringCoding.decode(StringCoding.java:193) at java.lang.StringCoding.decode(StringCoding.java:254) at java.lang.String.<init>(String.java:536) at java.lang.String.<init>(String.java:556) at org.apache.tools.ant.util.LineOrientedOutputStream.processLine(LineOrientedOutputStream.java:107)
Created attachment 144137 [details] stacktrace
There is 1,600,000 instances of org.netbeans.modules.gsf.testrunner.api.OutputLine. Most of them are hold by org.netbeans.modules.junit.output.JUnitTestcase#3. Its output instance variable contains ArrayList instance with 1,500,000 instances of OutputLine. Reassiging to java/junit for further evaluation.
Changeset: 664e1259433e Author: Theofanis Oikonomou <theofanis@netbeans.org> Date: 2014-01-31 13:06 Message:
As the OutputLines objects are stored in order to display a tooltip in the TRW suite/method nodes there is no reason to hold so much data, as at most TestsuiteNode.MAX_TOOLTIP_LINES lines will be displayed in the tooltip. In any case the output is visible both in output window and in the TRW's output pane. Thank you for reporting
Integrated into 'main-silver', will be available in build *201402020001* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main-silver/rev/664e1259433e User: Theofanis Oikonomou <theofanis@netbeans.org> Log: Task #240688 - OutOfMemoryError: Java heap space