Bug #23512 | native memory leak using prepared statements | ||
---|---|---|---|
Submitted: | 20 Oct 2006 18:29 | Modified: | 23 Oct 2006 14:40 |
Reporter: | Mark Strecker | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | Connector / J | Severity: | S2 (Serious) |
Version: | 5.0.3 | OS: | Linux (SUSE Linux 9.2) |
Assigned to: | Mark Matthews | CPU Architecture: | Any |
[20 Oct 2006 18:29]
Mark Strecker
[23 Oct 2006 14:40]
Mark Matthews
Our JDBC driver is Type-IV, which means it's pure java, so the driver itself can't be leaking native memory. If you see a native memory leak, it's a potential bug with your JVM, or it's "natural" overhead (there's memory the JVM needs to manage the heap that's not accounted for when you use a profiler that's only counting the size of objects in the heap, for example see http://forum.java.sun.com/thread.jspa?threadID=598888&messageID=3351661). You'd have to check with JVM vendor to determine which is the case.