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 236725 - OutOfMemoryError: Java heap space
Summary: OutOfMemoryError: Java heap space
Status: NEW
Alias: None
Product: platform
Classification: Unclassified
Component: Text (show other bugs)
Version: 7.4
Hardware: All All
: P3 normal (vote)
Assignee: Miloslav Metelka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-03 23:46 UTC by pinbender
Modified: 2013-10-18 14:16 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 204352

Attachments
stacktrace (2.38 KB, text/plain)
2013-10-03 23:46 UTC, pinbender 		Details
Thread dump from the slowness (368.61 KB, text/plain)
2013-10-18 14:15 UTC, Tomas Hurka 		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 pinbender 2013-10-03 23:46:13 UTC 
Build: NetBeans IDE Dev (Build nbms-and-javadoc-524-on-20130919)
VM: Java HotSpot(TM) Client VM, 23.25-b01, Java(TM) SE Runtime Environment, 1.7.0_25-b17
OS: Windows 7

User Comments:
pinbender: No idea.  I was just working like always, and noticed it had been saving a snapshot for a very, very long time.  I exited, and this happened when I restarted.




Stacktrace: 
java.lang.OutOfMemoryError: Java heap space
   at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:0)
   at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:0)
   at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:0)
   at java.util.TreeMap.writeObject(TreeMap.java:0)
   at sun.reflect.GeneratedMethodAccessor290.invoke(GeneratedMethodAccessor290.java:0)
   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:0)
Comment 1 pinbender 2013-10-03 23:46:14 UTC 
Created attachment 140785 [details]
stacktrace
Comment 2 Tomas Hurka 2013-10-18 14:15:30 UTC 
Created attachment 141261 [details]
Thread dump from the slowness

OOME is caused by really long stacktrcaes from C/C++ parsing. I was able to extract one stacktrace of the AWT slowness from heapdump and I am attaching it.
Comment 3 Tomas Hurka 2013-10-18 14:16:19 UTC 
From the stacktrace it looks like AWT is blocked by "org.openide.text Document Processing" thread. Reassigning to openide.text. Please investigate.