[
https://issues.apache.org/jira/browse/WICKET-5147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13640267#comment-13640267
]
Martin Grigorov commented on WICKET-5147:
-----------------------------------------
We will fix the issue for Wicket 6.8.0. I'm just trying to tell you that you
hit OOM because your tests leak resources.
Cookie class is quite small. You have to produce a lot of instances to fill the
memory. I doubt that you create so many cookies in a single test to run out of
memory. It is just that resources from a previous usage of WicketTester are not
recycled during the whole run of the test suite.
I see you reuse the application instance for the different instances of
WicketTester. This is already a candidate for memory leaks.
I guess you do this to avoid costly initializations, like initializing Spring
for example.
> WicketTester MockHttpRequest.getCookies very slow / OutOfMemory
> ---------------------------------------------------------------
>
> Key: WICKET-5147
> URL: https://issues.apache.org/jira/browse/WICKET-5147
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 6.7.0
> Reporter: Rob Audenaerde
> Attachments: testcookies.zip
>
>
> We have an extensive set of WicketTester tests. Recently, the wicket RELEASE
> in the maven repository changed to 6.7.0. After the new version, our tests
> got very slow.
> When profiling, I discovered that the MockHttpRequest.getCookies() was taking
> up a lot of time. Also, tests failed because of OutOfMemory exceptions. My
> guess is that somehow a lot of objects are created at such speeds that the GC
> cannot clean them
> I will investigate further, but switching back to 6.6.0 solved the issue.
> [Edit]
> The tests are run with TestNG and using 'mvn test'
--
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
