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.

Bug 258202

Summary:	OutOfMemoryError: Java heap space
Product:	updatecenters	Reporter:	thmarx <thmarx>
Component:	Pluginportal	Assignee:	attila.kelemen
Status:	NEW ---
Severity:	normal
Priority:	P3
Version:	8.1
Hardware:	All
OS:	All
Issue Type:	DEFECT	Exception Reporter:	212487
Attachments:	stacktrace

Description thmarx 2016-03-01 14:32:39 UTC

Build: NetBeans IDE 8.1 (Build 201510222201)
VM: Java HotSpot(TM) 64-Bit Server VM, 25.74-b02, Java(TM) SE Runtime Environment, 1.8.0_74-b02
OS: Windows 7

User Comments:
GUEST: Happens every time the background project scan takes place.

thmarx: running gradle tests

GUEST: Nothing. The IDE was idle. I shut it down and did not know there was a problem.

GUEST: Imported formatting options from https://github.com/bobsta63/netbeans-psr-formatting




Stacktrace: 
java.lang.OutOfMemoryError: Java heap space
   at com.sun.org.apache.xerces.internal.util.XMLStringBuffer.append(XMLStringBuffer.java:208)
   at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.scanData(XMLEntityScanner.java:1428)
   at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanCDATASection(XMLDocumentFragmentScannerImpl.java:1655)
   at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:3017)
   at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:606)
   at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510)

Comment 1 thmarx 2016-03-01 14:32:41 UTC

Created attachment 158694 [details]
stacktrace

Comment 2 Tomas Hurka 2016-03-02 13:22:04 UTC

It looks like the gradle test output has 300M.

Comment 3 Tomas Hurka 2016-03-02 13:23:13 UTC

Problem seems to be in NetBeans-Gradle integration https://github.com/kelemen/netbeans-gradle-project

Comment 4 Jiri Kovalsky 2016-03-02 21:15:06 UTC

Attila, can you please take a look at this issue? Thanks!

Comment 5 attila.kelemen 2016-03-02 22:15:00 UTC

(In reply to Jiri Kovalsky from comment #4)
> Attila, can you please take a look at this issue? Thanks!

I will have a look at it on friday most likely. Until then, my blind guess is that the standard output / error the tests generate are large and it has to be provided to the testing classes. If this is the case, what is the expected behaviour? Should I trim the standard output/error?

Comment 6 attila.kelemen 2016-03-07 18:46:04 UTC

Since there is nothing to reproduce the issue with, I have to guess. The only thing which can grow too large - in reasonable cases - is the text written to the standard output and the standard error. Therefore, I assume that that this is the issue.

Would it be an acceptable solution to somehow limit / disable the output text collection? This is the only way, I can think to solve this issue because I actually have to pass these outputs the NB's testing classes as a String instance.