[
https://issues.apache.org/jira/browse/DERBY-5336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-5336:
--------------------------------------
Component/s: (was: Miscellaneous)
Services
Issue & fix info: [Repro attached, Workaround attached] (was: [Repro
attached])
Bug behavior facts: [Crash, Regression] (was: [Crash])
I'm able to reproduce the OOME on trunk. It looks like the objects belonging to
the stopped database instances are still referenced from the index statistics
update daemon and cannot be freed.
Disabling automatic update of index statistics seems to work around the
problem. If I run the repro with -Dderby.storage.indexStats.auto=false, I don't
see the OOME.
I'm marking this bug as a regression, since the OOME is not seen with 10.7.1.1.
> Repeated database creation causes OutOfMemoryError
> --------------------------------------------------
>
> Key: DERBY-5336
> URL: https://issues.apache.org/jira/browse/DERBY-5336
> Project: Derby
> Issue Type: Bug
> Components: Services
> Affects Versions: 10.8.1.2
> Environment: Windows 7 64-bit, jdk1.6.0_26
> Reporter: Aja Walker
> Attachments: DerbyOutOfMemoryErrorRepro.java
>
>
> Repeatedly creating, querying, updating, and shutting down a database or
> databases eventually causes OutOfMemoryError.
> Java source reproducing the problem is attached.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
