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 244927 - OutOfMemoryError: GC overhead limit exceeded
Summary: OutOfMemoryError: GC overhead limit exceeded
Status: RESOLVED DUPLICATE of bug 245293
Alias: None
Product: java
Classification: Unclassified
Component: Compiler (show other bugs)
Version: 7.4
Hardware: All All
: P3 normal (vote)
Assignee: Dusan Balek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-06 16:22 UTC by rider453
Modified: 2014-07-24 13:25 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 210136

Attachments
stacktrace (2.38 KB, text/plain)
2014-06-06 16:22 UTC, rider453 		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 rider453 2014-06-06 16:22:37 UTC 
Build: NetBeans IDE 7.4 (Build 201310111528)
VM: Java HotSpot(TM) 64-Bit Server VM, 24.55-b03, Java(TM) SE Runtime Environment, 1.7.0_55-b13
OS: Windows 7

User Comments:
rider453: Hi
I was copying a code, then a saved changed by then netbeans was blocked.
Thanks




Stacktrace: 
java.lang.OutOfMemoryError: GC overhead limit exceeded
   at java.util.Arrays.copyOfRange(Arrays.java:2694)
   at java.lang.String.<init>(String.java:203)
   at java.lang.StringBuilder.toString(StringBuilder.java:405)
   at com.sun.java.swing.plaf.windows.TMSchema$Part.toString(TMSchema.java:216)
   at com.sun.java.swing.plaf.windows.AnimationController$PartUIClientPropertyKey.toString(AnimationController.java:425)
   at javax.swing.JComponent.putClientProperty(JComponent.java:4091)
Comment 1 rider453 2014-06-06 16:22:39 UTC 
Created attachment 147595 [details]
stacktrace
Comment 2 Tomas Hurka 2014-06-27 12:07:32 UTC 
A lot of javac classes on top of the heap histogram. The OOME is probably caused by parsing file in java.lang.String#168615.
Comment 3 Dusan Balek 2014-07-24 13:25:13 UTC 
The same problem as #245293.

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