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 243450

Summary:	OutOfMemoryError: GC overhead limit exceeded
Product:	db	Reporter:	kwoodle
Component:	MySQL	Assignee:	Libor Fischmeistr <lfischmeistr>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	kRk
Priority:	P3
Version:	7.4
Hardware:	All
OS:	All
Issue Type:	DEFECT	Exception Reporter:	207454
Attachments:	stacktrace

Description kwoodle 2014-04-01 13:31:35 UTC

Build: NetBeans IDE 7.4 (Build 201310111528)
VM: Java HotSpot(TM) 64-Bit Server VM, 23.21-b01, Java(TM) SE Runtime Environment, 1.7.0_21-b11
OS: Windows 7

User Comments:
kwoodle: select * from db.table never returns when acting on db shown in Services Window. Returns when limit no of rows. Increased packet size from 4 MB to 10 MB

GUEST: Background scanning... I really only have to turn NetBeans on to produce this error. I assume it has something to do with Action Items/CodeSniffer/MessDetectorbecause this error only occured after I set the scope for these items to package, and it started occuring after that. I have, however, set the scope back to file. This has had no effect on the occurance of the error.




Stacktrace: 
java.lang.OutOfMemoryError: GC overhead limit exceeded
   at java.lang.Class.getDeclaredMethods0(Class.java:0)
   at java.lang.Class.privateGetDeclaredMethods(Class.java:2451)
   at java.lang.Class.getMethod0(Class.java:2694)
   at java.lang.Class.getMethod(Class.java:1622)
   at org.openide.util.WeakListenerImpl$ListenerReference.getRemoveMethod(WeakListenerImpl.java:615)
   at org.openide.util.WeakListenerImpl$ListenerReference.run(WeakListenerImpl.java:573)

Comment 1 kwoodle 2014-04-01 13:31:37 UTC

Created attachment 146473 [details]
stacktrace

Comment 2 Petr Cyhelsky 2014-04-04 09:00:34 UTC

caused by executing select * from some big database which returns huge amount of data (in one of the heap dumps there are ~2.1M results in one ArrayList)

Comment 3 matthias42 2014-08-13 12:20:34 UTC

*** Bug 243850 has been marked as a duplicate of this bug. ***

Comment 4 matthias42 2014-10-06 21:58:54 UTC

Comment 2 from Petr Cyhelsky  points to most probable cause: To many rows are fetched by the JDBC driver. Closing as duplicate.

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