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 240155 - OutOfMemoryError: GC overhead limit exceeded
Summary: OutOfMemoryError: GC overhead limit exceeded
Status: RESOLVED DUPLICATE of bug 239611
Alias: None
Product: db
Classification: Unclassified
Component: SQL Editor (show other bugs)
Version: 7.4
Hardware: All All
: P3 normal (vote)
Assignee: Libor Fischmeistr
URL:
Keywords:
: 240137 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-01-09 11:18 UTC by Exceptions Reporter
Modified: 2014-01-18 13:44 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 206421

Attachments
stacktrace (312 bytes, text/plain)
2014-01-09 11:18 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-09 11:18:57 UTC 
This issue was reported manually by thurka.
It already has 1 duplicates 


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

User Comments:
GUEST: Did an SQL query to a rather large database table.




Stacktrace: 
java.lang.OutOfMemoryError: GC overhead limit exceeded
   at java.lang.String.toCharArray(String.java:2753)
   at java.lang.Thread.setName(Thread.java:1140)
   at org.openide.util.RequestProcessor.enqueue(RequestProcessor.java:619)
   at org.openide.util.RequestProcessor$TickTac.run(RequestProcessor.java:2243)
Comment 1 Exceptions Reporter 2014-01-09 11:18:58 UTC 
Created attachment 143745 [details]
stacktrace
Comment 2 matthias42 2014-01-09 11:38:38 UTC 
thurka, could you please state the database and if possible also the JDBC URL (if there is sensitive information, please replace it with some marker) you used when this happend?
Comment 3 Tomas Hurka 2014-01-09 12:02:09 UTC 
OOME is caused by SQL query, which returns a lot of rows. Retained size of  oracle.jdbc.driver.ScrollableResultSet#1 is 630M and there is 7,138,053 instances of oracle.jdbc.driver.CachedRowElement
Comment 4 matthias42 2014-01-09 12:08:12 UTC 
Thank you Thomas, could you please check the connection properties? Make sure that you are not connected.

I asume, that "Use scrollable cursors" is checked - please uncheck that option, connect and try again. This basicly disables the new scrollable cursor support (oracle jdbc driver simulates scrollable cursors and does not use the server). This looks like a duplicate of bug #239611.
Comment 5 Tomas Hurka 2014-01-09 12:16:37 UTC 
(In reply to matthias42 from comment #2)
> thurka, could you please state the database and if possible also the JDBC
> URL (if there is sensitive information, please replace it with some marker)
> you used when this happend?
I am not the reporter. I am evaluation several OOME incorrectly grouped into one exception report. 
It looks like database is Oracle Database 11g Enterprise Edition Release 11.2.0.3.0
Comment 6 Tomas Hurka 2014-01-09 17:37:37 UTC 
*** Bug 240137 has been marked as a duplicate of this bug. ***
Comment 7 matthias42 2014-01-18 13:44:58 UTC 

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