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 250915 - OutOfMemoryError: Java heap space
Summary: OutOfMemoryError: Java heap space
Status: NEW
Alias: None
Product: ide
Classification: Unclassified
Component: Logger (show other bugs)
Version: 8.0
Hardware: All All
: P4 normal (vote)
Assignee: Martin Entlicher
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-05 08:31 UTC by Exceptions Reporter
Modified: 2015-09-14 13:54 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 215860

Attachments
stacktrace (2.26 KB, text/plain)
2015-03-05 08:31 UTC, Exceptions Reporter 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Exceptions Reporter 2015-03-05 08:31:51 UTC 
This bug was originally marked as duplicate of bug 240227, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.

Build: NetBeans IDE 8.0.2 (Build 201411181905)
VM: Java HotSpot(TM) Client VM, 25.0-b70, Java(TM) SE Runtime Environment, 1.8.0-b132
OS: Windows 7

User Comments:
GUEST: i don't know what happen




Stacktrace: 
java.lang.OutOfMemoryError: Java heap space
   at java.util.Arrays.copyOf(Arrays.java:3326)
   at java.lang.AbstractStringBuilder.expandCapacity(AbstractStringBuilder.java:137)
   at java.lang.AbstractStringBuilder.ensureCapacityInternal(AbstractStringBuilder.java:121)
   at java.lang.AbstractStringBuilder.append(AbstractStringBuilder.java:421)
   at java.lang.StringBuilder.append(StringBuilder.java:136)
   at org.netbeans.core.startup.logging.PrintStreamLogger.print(PrintStreamLogger.java:108)
Comment 1 Exceptions Reporter 2015-03-05 08:31:53 UTC 
Created attachment 152406 [details]
stacktrace
Comment 2 Tomas Hurka 2015-04-03 14:02:42 UTC 
org.netbeans.core.startup.logging.PrintStreamLogger.sb (StringBuilder#4524) has length 54,525,900 chars. PrintStreamLogger should not allow 'sb' to be that big. it should flush the data from 'sb' more aggressively in above case.
Comment 3 Antonin Nebuzelsky 2015-09-14 13:54:17 UTC 
The root problem for the user is the neverending stream of java.net.SocketException in the log.

But flushing of data in log might be considered.