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 241558 - OutOfMemoryError: Java heap space
Summary: OutOfMemoryError: Java heap space
Status: RESOLVED DUPLICATE of bug 239025
Alias: None
Product: editor
Classification: Unclassified
Component: Parsing & Indexing (show other bugs)
Version: 7.4
Hardware: All All
: P3 normal (vote)
Assignee: Tomas Zezula
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-08 00:01 UTC by mithereal
Modified: 2014-02-25 09:56 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 207397


Attachments
stacktrace (822 bytes, text/plain)
2014-02-08 00:01 UTC, mithereal
Details

Note You need to log in before you can comment on or make changes to this bug.
Description mithereal 2014-02-08 00:01:51 UTC
Build: NetBeans IDE 7.4 (Build 201310111528)
VM: Java HotSpot(TM) 64-Bit Server VM, 24.51-b03, Java(TM) SE Runtime Environment, 1.7.0_51-b13
OS: Linux

User Comments:
mithereal: tried refactoring a folder name, last time i was trying to change folder name in projects via properties




Stacktrace: 
java.lang.OutOfMemoryError: Java heap space
   at java.util.Arrays.copyOfRange(Arrays.java:2694)
   at java.lang.String.<init>(String.java:203)
   at java.lang.String.substring(String.java:1913)
   at org.netbeans.ProxyClassLoader.loadClass(ProxyClassLoader.java:163)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
   at org.netbeans.modules.sampler.InternalSampler.createInternalSampler(InternalSampler.java:83)
Comment 1 mithereal 2014-02-08 00:01:52 UTC
Created attachment 144926 [details]
stacktrace
Comment 2 Tomas Hurka 2014-02-10 15:40:27 UTC
java.util.HashMap#24145 has retained size about 450M. This HashMap seems to be a thread local variable held in the following instance variable: org.netbeans.modules.parsing.impl.indexing.FileEventLog#1.changes

Reassigning to editor/parsing for further evaluation.
Comment 3 Tomas Zezula 2014-02-25 09:56:11 UTC

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