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] Commented: (DERBY-1142) Metadata calls leak memory
Date Mon, 10 Jul 2006 14:09:31 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1142?page=comments#action_12420085 ] 

Daniel John Debrunner commented on DERBY-1142:

An addition to the subset of changes of DERBY-827 fixed the issue, increasing the number of
iterations from ~10,000 to over a milllion with no error when limited to 10Mb of heap.
One part of the change is to close single use activations  in the close method of EmbedResultSet
rather than waiting for some other time, need to figure out what that time was. Will attach
the patch for this soon.
The second part is to mark EmbedResultSet as single use activations when they are created
for meta data.

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

>   Components: JDBC
>     Versions:,
>     Reporter: Knut Anders Hatlen
>     Assignee: Daniel John Debrunner
>     Priority: Minor
>  Attachments: 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:
For more information on JIRA, see:

View raw message