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 239599 - OutOfMemoryError: Java heap space
Summary: OutOfMemoryError: Java heap space
Status: RESOLVED WONTFIX
Alias: None
Product: db
Classification: Unclassified
Component: Show Data (show other bugs)
Version: 7.4
Hardware: All All
: P3 normal (vote)
Assignee: Libor Fischmeistr
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-18 11:07 UTC by Exceptions Reporter
Modified: 2013-12-18 13:10 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 206057


Attachments
stacktrace (1.68 KB, text/plain)
2013-12-18 11:07 UTC, Exceptions Reporter
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Exceptions Reporter 2013-12-18 11:07:23 UTC
This issue was reported manually by alexvsimon.
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-b15
OS: Linux

User Comments:
GUEST: <Please provide a description of the problem or the steps to reproduce>

8 gig of memory and this happens alot.




Stacktrace: 
java.lang.OutOfMemoryError: Java heap space
   at java.util.Arrays.copyOfRange(Arrays.java:2694)
   at java.lang.String.<init>(String.java:203)
   at java.lang.StringBuilder.toString(StringBuilder.java:405)
   at org.netbeans.modules.cnd.api.xml.XMLDocReader$Parser.characters(XMLDocReader.java:300)
   at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.characters(AbstractSAXParser.java:543)
   at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:442)
Comment 1 Exceptions Reporter 2013-12-18 11:07:25 UTC
Created attachment 143295 [details]
stacktrace
Comment 2 Alexander Simon 2013-12-18 11:31:02 UTC
400 Mb in com.microsoft.sqlserver.jdbc.TDSReader
Reassign to evaluation.
Comment 3 Libor Fischmeistr 2013-12-18 13:10:31 UTC
It seems like the bug of the JDBC driver - WONTFIX.