[jira] Commented: (WICKET-1549) Memory leak with PropertyResolver (in running test suites)

["Johan Compagner (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595901#action_12595901 ] 

Johan Compagner commented on WICKET-1549:
-----------------------------------------

changed that MockWebApplication (the base class of wicket tester) will call destroy on the real application object.

> Memory leak with PropertyResolver (in running test suites)
> ----------------------------------------------------------
>
>                 Key: WICKET-1549
>                 URL: https://issues.apache.org/jira/browse/WICKET-1549
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.3.2
>            Reporter: Teppo Kurki
>            Assignee: Johan Compagner
>            Priority: Minor
>             Fix For: 1.3.4, 1.4-M2
>
>
> Memory requirement  for running the test suite for a Wicket application increase as the number of constructed Applications (for example BaseWicketTester.DummyWebApplication) goes up.
> The static applicationToClassesToGetAndSetters Map holds Applications as keys. There is no equals/hashCode so a reference for each newly constructed test Application will be stuffed in there and not reused for identical Applications.
> I solved the problem for my project by implementing equals & hashCode in our DummyProjectXApplication.
> There seems to be something related going on in WICKET-625 with Application.internalDestroy, which removes the Application reference when the webapp is unloaded. After a test is done with the Application it might use the same mechanism for "unloading" the application?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.