[
https://issues.apache.org/jira/browse/DERBY-3713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644110#action_12644110
]
Kathey Marsden commented on DERBY-3713:
---------------------------------------
Should this issue be closed invalid assuming that the normal cache growth is
the issue?
> memory leak when insert rows into a table using
> org.apache.derby.jdbc.EmbeddedDriver
> -------------------------------------------------------------------------------------
>
> Key: DERBY-3713
> URL: https://issues.apache.org/jira/browse/DERBY-3713
> Project: Derby
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 10.4.1.3
> Environment: solaris and macos, jdk1.5
> Reporter: Peter Schi
>
> I downloaded the latest derby and I only modified the SimpleApp.java which
> came with the software under db-derby-10.4.1.3-bin/demo/programs/simple
> directory by inserting a larger string into the same table and I inserted the
> same data for 10000 times, just using the default driver which was
> org.apache.derby.jdbc.EmbeddedDriver
> I found out that there was memory leak, the size of used memory got increased
> and was about the same size of total data inserted into the table.
> For example, if 2MB size of data was inserted into the table, then the size
> of used memory was increased by 2MB as well.
> The memory leak still happened even if the database was shut down.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
