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.
This bug was originally marked as duplicate of bug 239570, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related. Build: NetBeans IDE 8.0 (Build 201403101706) VM: Java HotSpot(TM) 64-Bit Server VM, 24.60-b09, Java(TM) SE Runtime Environment, 1.7.0_60-b19 OS: Windows 7 User Comments: jfinkel: Opening a file. GUEST: In the Databases panel clicked on a large Oracle table and selected View Data expecting it would page the results but it appeared to hang while trying to fetch the entire (milti million row) table and finally after more than an hour I had to kill Netbeans. Stacktrace: java.lang.OutOfMemoryError: Java heap space at java.util.Arrays.copyOf(Arrays.java:2367) at java.lang.String.<init>(String.java:168) at java.lang.String.valueOf(String.java:2861) at java.lang.Thread.getName(Thread.java:1171) at org.openide.util.RequestProcessor$Processor.put(RequestProcessor.java:1933) at org.openide.util.RequestProcessor.askForWork(RequestProcessor.java:635)
Created attachment 148811 [details] stacktrace
Retained size of 3088 instances org.netbeans.modules.db.explorer.node.ColumnNode is 250,646,872. This represents 35.6% of entire heap. Reassigning to db module for further investigation.
I'll close this as a duplicate of 239611. Oracle does not properly support scrollable cursors and when requesting them leads to client side caching, that in this case most probably flooded the heap. The fix is easy: Disable scrollable cursors and the old behavior is reinstated (check the connection properties of the connection). For bug 239611 a patch was committed, that fixes this for new connections. *** This bug has been marked as a duplicate of bug 239611 ***