[
https://issues.apache.org/jira/browse/WICKET-4819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Grigorov resolved WICKET-4819.
-------------------------------------
Resolution: Not A Problem
Miracles happen when you close your resources after using them ;-)
Add "tester.destroy();" at the bottom and it suddenly works.
> Memory Leak in WicketTester
> ---------------------------
>
> Key: WICKET-4819
> URL: https://issues.apache.org/jira/browse/WICKET-4819
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.1.1
> Environment: Linux, openjdk 7
> Reporter: Peter Henderson
> Priority: Minor
> Labels: leak, test
> Attachments: myproject.tar.gz
>
>
> I though I'd test every page in an app for every DB record, (Mad I know).
> Attached is quick start slowly grinds to a halt when testing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
