db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Digulla (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-4444) Suspected memory leak in Import.importData()
Date Mon, 16 Nov 2009 11:53:39 GMT

    [ https://issues.apache.org/jira/browse/DERBY-4444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778304#action_12778304
] 

Aaron Digulla commented on DERBY-4444:
--------------------------------------

I tried to profile the issue and it seems that DynamicByteArrayOutputStream is involved but
I couldn't nail it down and now, I'm running out of time to pursue the issue further. Maybe
someone forgot to call close() on it?

> Suspected memory leak in Import.importData()
> --------------------------------------------
>
>                 Key: DERBY-4444
>                 URL: https://issues.apache.org/jira/browse/DERBY-4444
>             Project: Derby
>          Issue Type: Bug
>    Affects Versions: 10.4.2.0, 10.5.3.0
>            Reporter: Aaron Digulla
>
> When calling Import.importData() repeatedly (for example, via SystemProcedures.SYSCS_IMPORT_DATA),
then the VM will eventually run out of memory.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message