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 231565 - OutOfMemoryError: Java heap space
Summary: OutOfMemoryError: Java heap space
Status: RESOLVED WONTFIX
Alias: None
Product: java
Classification: Unclassified
Component: Source (show other bugs)
Version: 7.4
Hardware: All All
: P3 normal (vote)
Assignee: Svata Dedic
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-20 11:44 UTC by Ondrej Vrabec
Modified: 2013-09-13 09:05 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 201566


Attachments
stacktrace (1.84 KB, text/plain)
2013-06-20 11:44 UTC, Ondrej Vrabec
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ondrej Vrabec 2013-06-20 11:44:12 UTC
Build: NetBeans IDE Dev (Build 20130617-ab3512bc7eab)
VM: Java HotSpot(TM) 64-Bit Server VM, 23.25-b01, Java(TM) SE Runtime Environment, 1.7.0_25-b15
OS: Linux

User Comments:
ovrabec: navigating to a method inside jdk sources (inside BasicTreeUI)




Stacktrace: 
java.lang.OutOfMemoryError: Java heap space
   at sun.text.UCompactIntArray.initPlane(UCompactIntArray.java:160)
   at sun.text.UCompactIntArray.setElementAt(UCompactIntArray.java:73)
   at java.text.RBTableBuilder.addOrder(RBTableBuilder.java:342)
   at java.text.RBTableBuilder.build(RBTableBuilder.java:154)
   at java.text.RBCollationTables.<init>(RBCollationTables.java:83)
   at java.text.RuleBasedCollator.<init>(RuleBasedCollator.java:300)
Comment 1 Ondrej Vrabec 2013-06-20 11:44:13 UTC
Created attachment 136077 [details]
stacktrace
Comment 2 Martin Entlicher 2013-06-24 14:35:32 UTC
The memory is consumed by Java parsers.
Here are the top retained sizes:
com.sun.tools.javac.tree.JCTree$JCCompilationUnit	339,035,331 (30.3%)
java.util.HashMap					323,386,265 (28.9%)
org.netbeans.lib.nbjavac.services.NBParserFactory$NBJavacParser$EndPosTableImpl
							319,953,335 (28.6%)
There are 3,561 instances of parser and associated classes.
Comment 3 Svata Dedic 2013-09-13 09:05:50 UTC
The number of NbJavacParsers could correspond to the number of source files, IMHO. The indexing system contains some counter-measures against running OOM, but it seems the huge compilation task was requested by debugger, so it runs without those safeguards.