[ http://issues.apache.org/jira/browse/DERBY-1142?page=comments#action_12429260 ] Mayuresh Nirhali commented on DERBY-1142: -----------------------------------------
If the singleUseActivation is closed in the finalize method of EmdebResultSet then the memory leak is not observed even in this extreme case. While, this may not be a complete fix, but certainly one of fixes. Please see DERBY-418 for more details. > Metadata calls leak memory > -------------------------- > > Key: DERBY-1142 > URL: http://issues.apache.org/jira/browse/DERBY-1142 > Project: Derby > Issue Type: Bug > Components: JDBC > Affects Versions: 10.1.2.1, 10.2.1.0 > Reporter: Knut Anders Hatlen > 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
