db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1142) Metadata calls leak memory
Date Mon, 10 Jul 2006 14:18:34 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1142?page=all ]

Daniel John Debrunner updated DERBY-1142:
-----------------------------------------

    Attachment: 1142_close_single_use_activations_draft.txt

Draft patch that closes an EmbedResultSet's single use activation when the result set is closed.
Previously the activations' close would have been delayed until after the EmbedResultSet was
garbage collected and some activilty occured in the connection that caused the list of activations
to be scanned. Comment needs some comments before being applied.

> Metadata calls leak memory
> --------------------------
>
>          Key: DERBY-1142
>          URL: http://issues.apache.org/jira/browse/DERBY-1142
>      Project: Derby
>         Type: Bug

>   Components: JDBC
>     Versions: 10.1.2.1, 10.2.0.0
>     Reporter: Knut Anders Hatlen
>     Assignee: Daniel John Debrunner
>     Priority: Minor
>  Attachments: 1142_close_single_use_activations_draft.txt, metadataloop.java
>
> When calling a DatabaseMetaData method that returns a ResultSet,
> memory is leaked. A loop like this (using the embedded driver)
>   while (true) {
>     ResultSet rs = dmd.getSchemas();
>     rs.close();
>   }
> will eventually cause an OutOfMemoryError.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message