[
https://issues.apache.org/jira/browse/DERBY-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536727
]
Kathey Marsden commented on DERBY-3140:
---------------------------------------
Kristian Waagan said:
>I guess this also means that larger data structures required for testing
>should be made static if >possible?
I think they should be avoided if possible and localized to the fixtures. If
that is not possible they should be nulled out as proposed for
InListMultiProbeTest
>As far as I know, JUnit creates a new instance of the class for each test (or
>test method).
Looking at the instance snapshot attached, it looks like most of the tests have
one instance for the embedded run and one for Network Server. However some
tests like ClosedObjectTest (3510 instances) have many more. I haven't looked
at that test to see exactly what's going on. I am not sure yet if we could
avoid all of this with a different TestRunner which might get rid of references
after the test is run.
> InListMultiProbeTest creates 30000 DataRow objects that do not get released
> during suites.All run
> -------------------------------------------------------------------------------------------------
>
> Key: DERBY-3140
> URL: https://issues.apache.org/jira/browse/DERBY-3140
> Project: Derby
> Issue Type: Sub-task
> Components: Test
> Affects Versions: 10.4.0.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Minor
> Attachments: derby-3140_diff.txt, Snapshotinstancecounts.html
>
>
> Using jhat I noticed that there are 30000 DataRow object created by
> InListMultiProbeTest that do not get released after the test is complete.
> This is because foreignIdToRowsMap is declared as a field in the test.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
