[ https://issues.apache.org/jira/browse/DERBY-5336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-5336:
-----------------------------------
Attachment: derby-5336-2a-regression_test.diff
Thanks, Aja.
Attaching patch 2a, where I copied Aja's repro and modified it to fit with the Derby test
framework (JUnit based):
- switched from DriverManager to DataSource
- replaced commons io call to delete directory
- added an extra sanity check
- added test as testRepeatedDatabaseCreationWithAutoStats in memory.MemoryLeakFixesTest.
Should be run with 'ant junit-lowmem' (after building Derby), which uses a 16 MB heap.
The test failed when run without the fix, it succeeded with patch 1a applied.
Patch ready for review.
> 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
> Assignee: Kristian Waagan
> Attachments: DerbyOutOfMemoryErrorRepro.java, LicensedRepro.java, derby-5336-1a-remove_context_on_stop.diff,
derby-5336-2a-regression_test.diff
>
>
> 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
|