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 247602 - OutOfMemoryError: GC overhead limit exceeded
Summary: OutOfMemoryError: GC overhead limit exceeded
Status: RESOLVED DUPLICATE of bug 253771
Alias: None
Product: javascript
Classification: Unclassified
Component: Editor (show other bugs)
Version: 8.0
Hardware: All All
: P3 normal (vote)
Assignee: Petr Pisl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-30 16:41 UTC by ktincheva
Modified: 2015-09-09 12:42 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 212348


Attachments
stacktrace (1.18 KB, text/plain)
2014-09-30 16:41 UTC, ktincheva
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ktincheva 2014-09-30 16:41:27 UTC
Build: NetBeans IDE 8.0.1 (Build 201408251540)
VM: Java HotSpot(TM) 64-Bit Server VM, 25.11-b03, Java(TM) SE Runtime Environment, 1.8.0_11-b12
OS: Windows 8

User Comments:
ktincheva: The applicattion stop responding, when start checking for external changes. This caused CPU overload and memory overload.  I bought a new computer (8G RAM, I7 CPU), bacause i had the same problem with Netbean with my old laptop. But now i see that reasan is not in my device. Please coorect this i love this IDE. I don't wont to chage it.




Stacktrace: 
java.lang.OutOfMemoryError: GC overhead limit exceeded
   at java.lang.SecurityManager.checkPackageAccess(SecurityManager.java:1563)
   at java.lang.Class.checkPackageAccess(Class.java:2359)
   at java.lang.Class.checkMemberAccess(Class.java:2338)
   at java.lang.Class.getDeclaredFields(Class.java:1902)
   at com.sun.jna.Structure.getFieldList(Structure.java:866)
   at com.sun.jna.Structure.validateFields(Structure.java:1045)
Comment 1 ktincheva 2014-09-30 16:41:29 UTC
Created attachment 149626 [details]
stacktrace
Comment 2 Jaroslav Havlin 2014-10-01 08:24:56 UTC
From the heap dump (find GC root of the largest object -> Show in threads):
 
"Editor Parsing Loop (201408251540)" daemon prio=1 tid=25 RUNNABLE
    at java.util.Arrays.copyOfRange(Arrays.java:3658)
       Local Variable: char[]#2086551
    at java.lang.String.<init>(String.java:201)
    at java.lang.String.substring(String.java:1920)
    at org.netbeans.modules.javascript2.editor.index.JsIndex.getProperties(JsIndex.java:410)
       Local Variable: org.netbeans.modules.parsing.spi.indexing.support.IndexResult#259187
       Local Variable: java.util.ArrayList#445380
       Local Variable: java.util.Hashtable$Enumerator#1
    at org.netbeans.modules.javascript2.editor.index.JsIndex.getProperties(JsIndex.java:337)
    at org.netbeans.modules.javascript2.editor.model.impl.ModelUtils.resolveAssignments(ModelUtils.java:1226)
    at org.netbeans.modules.javascript2.editor.model.impl.ModelUtils.resolveAssignments(ModelUtils.java:1175)
    at org.netbeans.modules.javascript2.editor.model.impl.ModelUtils.resolveTypeFromExpression(ModelUtils.java:853)

Retained size of java.util.Hashtable$Enumerator#1 is 665 MB.
Seems related to bug 247036 (maybe duplicate).

Reassigning to javascript/Editor. Please evaluate. Thank you.
Comment 3 Petr Pisl 2015-09-07 13:13:17 UTC
The problem mentioned in the comment #2 is already solved. But there are also thread dumps from CND library manager and cnd. Reassigning for evaluation.
Comment 4 Jan Stola 2015-09-08 09:59:03 UTC
(In reply to Petr Pisl from comment #3)
> The problem mentioned in the comment #2 is already solved. But there are
> also thread dumps from CND library manager and cnd. Reassigning for
> evaluation.

There was only one report/heap-dump related to CDNJS libraries. I have separated this heap-dump into another issue. I am reassigning this issue back to javascript/Editor as the majority of the reports seem related to this component. I know that you mentioned that the corresponding problem is fixed. So, please, separate the heap-dumps that correspond to the fixed problem from the ones that you do not consider to be fixed and reassign the resulting issues appropriately. Thank you in advance.
Comment 5 Petr Pisl 2015-09-09 12:42:41 UTC
I have separated the other one and there are left only which are duplicates of issue #253771

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