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 172434 - [MAC] IDE hangs after some time (OutOfMemoryError: Java heap space)
Summary: [MAC] IDE hangs after some time (OutOfMemoryError: Java heap space)
Status: CLOSED INCOMPLETE
Alias: None
Product: ide
Classification: Unclassified
Component: Performance (show other bugs)
Version: 3.x
Hardware: All All
: P1 blocker (vote)
Assignee: issues@performance
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-17 08:00 UTC by Alexandr Scherbatiy
Modified: 2011-05-25 11:39 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
IDE log file (45.75 KB, text/plain)
2009-09-17 08:03 UTC, Alexandr Scherbatiy
Details
ThreadDump (8.18 KB, text/plain)
2009-09-17 08:03 UTC, Alexandr Scherbatiy
Details
Heap Dump > jmap -histo 5535 (339.04 KB, text/plain)
2009-10-06 10:01 UTC, Alexandr Scherbatiy
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Alexandr Scherbatiy 2009-09-17 08:00:54 UTC
OS: Mac

Steps to reproduce:
- Create a JavaFX project
- Run the project
- Close the project
- Leave the IDE for a long time 

The IDE hangs
Comment 1 Alexandr Scherbatiy 2009-09-17 08:02:24 UTC
java.lang.OutOfMemoryError: Java heap space
	at java.lang.String.<init>(String.java:208)
	at java.util.Properties.loadConvert(Properties.java:508)
	at java.util.Properties.load(Properties.java:331)
	at org.openide.util.NbBundle.loadBundle(NbBundle.java:559)
	at org.openide.util.NbBundle.getBundleFast(NbBundle.java:512)
	at org.openide.util.NbBundle.getBundle(NbBundle.java:438)
	at org.openide.util.NbBundle.getBundle(NbBundle.java:391)
	at org.openide.util.NbBundle.getMessage(NbBundle.java:634)
	at org.netbeans.modules.uihandler.UIHandler.call(UIHandler.java:160)
	at org.netbeans.modules.uihandler.UIHandler.call(UIHandler.java:65)
	at org.netbeans.core.NotifyExcPanel.computeOptions(NotifyExcPanel.java:215)
	at org.netbeans.core.NotifyExcPanel.<init>(NotifyExcPanel.java:166)
	at org.netbeans.core.NotifyExcPanel.<init>(NotifyExcPanel.java:92)
	at org.netbeans.core.NotifyExcPanel$2.run(NotifyExcPanel.java:326)
	at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
	at java.awt.EventQueue.dispatchEvent(EventQueue.java:461)
	at org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:117)
[catch] at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:269)
	at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:184)
	at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:176)
	at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
WARNING [org.netbeans.core.TimableEventQueue]: too much time in AWT thread 
org.netbeans.modules.profiler.actions.SelfSamplerAction$Controller@38f41
WARNING [org.netbeans.core.TimableEventQueue]: no snapshot taken

Comment 2 Alexandr Scherbatiy 2009-09-17 08:02:48 UTC
 Product Version         = NetBeans IDE Dev (Build 200909151512) (#ebf350cbb86b)
  Operating System        = Mac OS X version 10.5.6 running on i386
  Java; VM; Vendor        = 1.5.0_16; Java HotSpot(TM) Client VM 1.5.0_16-133; Apple Inc.

Comment 3 Alexandr Scherbatiy 2009-09-17 08:03:35 UTC
Created attachment 87809 [details]
IDE log file
Comment 4 Alexandr Scherbatiy 2009-09-17 08:03:54 UTC
Created attachment 87810 [details]
ThreadDump
Comment 5 Petr Suchomel 2009-09-23 09:24:44 UTC
Making this INCOMPLETE - please provide with more data. Leave IDE running "Leave the IDE for a long time" I am not sure
what the long time is and some time before you expect this problem to appear, take a snapshot by Profile me now or
connect by NB Profiler and get memory snaphot
Comment 6 Adam Sotona 2009-09-23 15:02:33 UTC
heap dump would help to analyze OOME
Comment 7 Tomas Pavek 2009-09-23 16:37:47 UTC
The IDE likely created the heap dump (it is set to do it by default when OutOfMemoryError happens). You can find the
location of the heap dump in the log file, e.g. use menu View | IDE Log and search for string -XX:HeapDumpPath

We'd need you to share the heap dump somewhere so we could download it. It's too big to attach to an issue report.

If you are able to reproduce the problem, you could also create a histogram that would also give us a hint what is
wrong, and it is much smaller. See http://wiki.netbeans.org/FaqMemoryDump.
Comment 8 Alexandr Scherbatiy 2009-10-06 10:01:11 UTC
Created attachment 88882 [details]
Heap Dump > jmap -histo 5535
Comment 9 Jaroslav Tulach 2009-10-14 16:30:34 UTC
Well, jmap histogram is not enough, I am afraid. I can see that there is 17M of ConstMethodKlass, 11M of SymbolKlass, 
8MB of ConstantPoolKlass, 8MB of MethodKlass, 6MB of InstanceKlassKlass, 5MB of ConstantPoolCacheKlass. I can also see 
that there is 50MB of LinkedList.Entry. But I need whole memory dump to find out who is referencing these objects. 
Please take heap dump (~400MB) and expose it for download on some server.