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 201093 - OutOfMemoryError: Java heap space
Summary: OutOfMemoryError: Java heap space
Status: RESOLVED INCOMPLETE
Alias: None
Product: db
Classification: Unclassified
Component: Show Data (show other bugs)
Version: 7.0
Hardware: All All
: P3 normal (vote)
Assignee: Jiri Rechtacek
URL:
Keywords:
: 189290 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-08-18 11:27 UTC by gmameli
Modified: 2012-09-29 20:39 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 180698

Attachments
stacktrace (1.95 KB, text/plain)
2011-08-18 11:27 UTC, gmameli 		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 gmameli 2011-08-18 11:27:45 UTC 
Build: NetBeans IDE 7.0.1 (Build 201107282000)
VM: Java HotSpot(TM) Client VM, 20.1-b02, Java(TM) SE Runtime Environment, 1.6.0_26-b03
OS: Windows 7

User Comments:
gmameli: Executing a query select * from TTMI.TTMI_TICKET A
    INNER JOIN (SELECT * FROM TTMI.TTMI_REVISIONI 
                    WHERE ROWNUM = 1 
                    ORDER BY ID_REVISIONE ASC) B
    ON A.ID_TICKET = B.ID_TICKET
WHERE A.ID_GDC=41
AND ID_STATO_TICKET=5
AND TRUNC(DATA_PRECHIUSURA) >= to_date('01/08/2011','dd/mm/yyyy') 
AND TRUNC(DATA_PRECHIUSURA) <= to_date('31/08/2011','dd/mm/yyyy')




Stacktrace: 
java.lang.OutOfMemoryError: Java heap space
   at java.lang.reflect.Array.newArray(Array.java:0)
   at java.lang.reflect.Array.newInstance(Array.java:52)
   at oracle.jdbc.driver.BufferCache.get(BufferCache.java:226)
   at oracle.jdbc.driver.PhysicalConnection.getCharBuffer(PhysicalConnection.java:7600)
   at oracle.jdbc.driver.OracleStatement.prepareAccessors(OracleStatement.java:991)
   at oracle.jdbc.driver.T4CTTIdcb.receiveCommon(T4CTTIdcb.java:273)
Comment 1 gmameli 2011-08-18 11:27:49 UTC 
Created attachment 110081 [details]
stacktrace
Comment 2 Jiri Rechtacek 2011-10-14 16:24:49 UTC 
The reporter, could you generate a heap dump when the problem appear again? It
help us to investigate the problem? How to generate heap dump -
http://wiki.netbeans.org/FaqMemoryDump Thank you
Comment 3 Jiri Rechtacek 2011-11-11 11:36:39 UTC 
*** Bug 189290 has been marked as a duplicate of this bug. ***
Comment 4 matthias42 2012-09-29 20:39:07 UTC 
The stack trace indicates the problem originates from the jdbc driver. There are so many parts in netbeans that could lead to filling the heap, that searching without a heapdump is pointless.

The heapdump was requested nearly a year ago. Closing bug. Feel free to reopen with more information.