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 254681 - OutOfMemoryError: GC overhead limit exceeded
Summary: OutOfMemoryError: GC overhead limit exceeded
Status: RESOLVED DUPLICATE of bug 253306
Alias: None
Product: editor
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 8.0
Hardware: All All
: P3 normal (vote)
Assignee: Milutin Kristofic
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-25 07:44 UTC by dhuyvetter
Modified: 2015-08-25 13:50 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 219410


Attachments
stacktrace (1.07 KB, text/plain)
2015-08-25 07:44 UTC, dhuyvetter
Details

Note You need to log in before you can comment on or make changes to this bug.
Description dhuyvetter 2015-08-25 07:44:53 UTC
Build: NetBeans IDE 8.0.2 (Build 201411181905)
VM: Java HotSpot(TM) 64-Bit Server VM, 25.60-b23, Java(TM) SE Runtime Environment, 1.8.0_60-b27
OS: Linux

User Comments:
dhuyvetter: This error seems to pop up every morning. Possible cause is that I don't close Netbeans correctly and just shut down computer, without closing Netbeans.




Stacktrace: 
java.lang.OutOfMemoryError: GC overhead limit exceeded
   at org.netbeans.lib.editor.util.GapList.allocateElementsArray(GapList.java:864)
   at org.netbeans.lib.editor.util.GapList.<init>(GapList.java:94)
   at org.netbeans.lib.editor.util.GapList.<init>(GapList.java:102)
   at org.netbeans.modules.editor.lib2.highlighting.AbstractOffsetGapList.<init>(AbstractOffsetGapList.java:130)
   at org.netbeans.modules.editor.lib2.highlighting.OffsetGapList.<init>(OffsetGapList.java:61)
   at org.netbeans.spi.editor.highlighting.support.OffsetsBag.<init>(OffsetsBag.java:127)
Comment 1 dhuyvetter 2015-08-25 07:44:55 UTC
Created attachment 155600 [details]
stacktrace
Comment 2 Milutin Kristofic 2015-08-25 13:50:30 UTC
Many RuleNodes, Netbeans IDE 8.0.2, it is similar to reports in Bug #253306

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