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 239541 - OutOfMemoryError: Java heap space
Summary: OutOfMemoryError: Java heap space
Status: RESOLVED DUPLICATE of bug 236773
Alias: None
Product: platform
Classification: Unclassified
Component: Filesystems (show other bugs)
Version: 7.4
Hardware: All All
: P3 normal (vote)
Assignee: Jaroslav Havlin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-17 00:19 UTC by leewilson86
Modified: 2013-12-17 07:50 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 206061

Attachments
stacktrace (2.99 KB, text/plain)
2013-12-17 00:19 UTC, leewilson86 		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 leewilson86 2013-12-17 00:19:19 UTC 
Build: NetBeans IDE 7.4 (Build 201310111528)
VM: Java HotSpot(TM) 64-Bit Server VM, 24.0-b56, Java(TM) SE Runtime Environment, 1.7.0_40-b43
OS: Mac OS X

User Comments:
leewilson86: I was just working innocently and it used about 800% of my CPU and over 1GB of RAM.

Please sort this out!




Stacktrace: 
java.lang.OutOfMemoryError: Java heap space
   at java.util.Arrays.copyOf(Arrays.java:2367)
   at java.lang.String.<init>(String.java:168)
   at org.openide.util.CharSequences$ByteBasedSequence.toString(CharSequences.java:1485)
   at org.netbeans.modules.masterfs.filebasedfs.naming.FileName.getName(FileName.java:114)
   at org.netbeans.modules.masterfs.filebasedfs.naming.FileName.getFile(FileName.java:109)
   at org.netbeans.modules.masterfs.filebasedfs.naming.NamingFactory.getReference(NamingFactory.java:347)
Comment 1 leewilson86 2013-12-17 00:19:21 UTC 
Created attachment 143230 [details]
stacktrace
Comment 2 Jaroslav Havlin 2013-12-17 07:50:34 UTC 
There are 8.6 million instances of org.openide.filesystems.FCLSupport$DispatchEventWrapper in the heap dump.
Probably duplicate of bug 236773.
Thank you for reporting.

*** This bug has been marked as a duplicate of bug 236773 ***