You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Knut Anders Hatlen (JIRA)" <ji...@apache.org> on 2010/01/25 19:55:34 UTC

[jira] Updated: (DERBY-4444) Suspected memory leak in Import.importData()

     [ https://issues.apache.org/jira/browse/DERBY-4444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Knut Anders Hatlen updated DERBY-4444:
--------------------------------------

    Attachment: input.dat
                ImportData.java

I tried to reproduce this issue with the attached program and data input file. After 2.5 million calls to SYSCS_UTIL.SYSCS_IMPORT_DATA, I still didn't see any memory issues. VisualVM also reported steady memory usage. I ran the program with the following command and with input.dat in the working directory:

    java -Dderby.system.durability=test -Xmx50M -XX:MaxPermSize=25M ImportData

What changes would I have to make to this program in order to reproduce the problem?

> 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
>         Attachments: ImportData.java, input.dat
>
>
> 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.