db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3140) InListMultiProbeTest creates 30000 DataRow objects that do not get released during suites.All run
Date Sat, 20 Oct 2007 22:35:50 GMT

    [ https://issues.apache.org/jira/browse/DERBY-3140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12536475
] 

Kristian Waagan commented on DERBY-3140:
----------------------------------------

I guess this also means that larger data structures required for testing should be made static
if possible?
As far as I know, JUnit creates a new instance of the class for each test (or test method).

This does of course require that the data can be shared this way.

> 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.


Mime
View raw message