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 268170 - OutOfMemoryError: GC overhead limit exceeded
Summary: OutOfMemoryError: GC overhead limit exceeded
Status: RESOLVED WONTFIX
Alias: None
Product: db
Classification: Unclassified
Component: Code (show other bugs)
Version: Dev
Hardware: All All
: P3 normal (vote)
Assignee: Libor Fischmeistr
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-23 10:22 UTC by AlxLy
Modified: 2016-12-01 19:05 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 221458

Attachments
stacktrace (993 bytes, text/plain)
2016-09-23 10:22 UTC, AlxLy 		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 AlxLy 2016-09-23 10:22:20 UTC 
Build: NetBeans IDE Dev (Build nbms-and-javadoc-595-on-20160906)
VM: OpenJDK 64-Bit Server VM, 25.101-b13, OpenJDK Runtime Environment, 1.8.0_101-b13
OS: Linux

User Comments:
AlxLy: SQL fetch without limit.

GUEST: I've written a java class, that length was 2224 lines. I think it was the reason of falling down of NetBeans.




Stacktrace: 
java.lang.OutOfMemoryError: GC overhead limit exceeded
   at java.lang.SecurityManager.getClassContext(SecurityManager.java:0)
   at org.netbeans.TopSecurityManager.checkWhetherAccessedFromSwingTransfer(TopSecurityManager.java:757)
   at org.netbeans.TopSecurityManager.checkPermission(TopSecurityManager.java:502)
   at java.awt.event.InputEvent.canAccessSystemClipboard(InputEvent.java:354)
   at java.awt.event.InputEvent.<init>(InputEvent.java:344)
   at java.awt.event.MouseEvent.<init>(MouseEvent.java:736)
Comment 1 AlxLy 2016-09-23 10:22:24 UTC 
Created attachment 162185 [details]
stacktrace
Comment 2 Tomas Hurka 2016-09-23 14:20:32 UTC 
Retained size of java.util.ArrayList#78263 is 736,187,693 bytes. This array
list is created by "SQLStatementExecution" thread.
Comment 3 matthias42 2016-12-01 19:05:37 UTC 
Various approaches were tried to limit memory utilization - the reasons were either bad jdbc drivers (fetching whole result instead of only the subset) or users trying to fetch the whole table.