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 240601 - OutOfMemoryError: GC overhead limit exceeded
Summary: OutOfMemoryError: GC overhead limit exceeded
Status: RESOLVED DUPLICATE of bug 239360
Alias: None
Product: editor
Classification: Unclassified
Component: Painting & Printing (show other bugs)
Version: 7.4
Hardware: All All
: P3 normal (vote)
Assignee: Miloslav Metelka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-17 12:37 UTC by Exceptions Reporter
Modified: 2014-01-17 13:12 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 206665

Attachments
stacktrace (1.17 KB, text/plain)
2014-01-17 12:37 UTC, Exceptions Reporter 		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 Exceptions Reporter 2014-01-17 12:37:03 UTC 
This issue was reported manually by jhavlin.
It already has 1 duplicates 


Build: NetBeans IDE 7.4 (Build 201310111528)
VM: Java HotSpot(TM) 64-Bit Server VM, 24.45-b08, Java(TM) SE Runtime Environment, 1.7.0_45-b18
OS: Windows 7

User Comments:
GUEST: Changing tabs to edit another java file.




Stacktrace: 
java.lang.OutOfMemoryError: GC overhead limit exceeded
   at java.lang.SecurityManager.checkPackageAccess(SecurityManager.java:1528)
   at java.lang.Class.checkPackageAccess(Class.java:2265)
   at java.lang.Class.checkMemberAccess(Class.java:2245)
   at java.lang.Class.getField(Class.java:1576)
   at com.sun.jna.Native.getStructureAlignment(Native.java:506)
   at com.sun.jna.Structure.setAlignType(Structure.java:237)
Comment 1 Exceptions Reporter 2014-01-17 12:37:05 UTC 
Created attachment 144071 [details]
stacktrace
Comment 2 Jaroslav Havlin 2014-01-17 13:12:36 UTC 
There are 367,596  instances of o.n.m.editor.lib2.highlighting.HighlightItem.
Retained size of all instances of o.n.m.editor.lib2.view.ParagraphView is 516 MB.

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