[
https://issues.apache.org/jira/browse/WICKET-5147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13640291#comment-13640291
]
Rob Audenaerde commented on WICKET-5147:
----------------------------------------
Hi Martin,
Thanks for the resolution. And you are right that I'm injecting the
WicketAppliction using Spring :)
BTW. The problem is not that the Cookie itself is big, but rather that going
through some ajax calls within one test causes the number of cookies to double
and double and double; so basically having one cookie will cause OOM after a
slightly bigger test, (for example 20 ajaxcalls will cause at least 2^20 (~ 1
million) cookies.).
Some context: In our application users can set filters in a few mouseclicks,
but to make sure they have to do as little as possible, I want to remove all
the options that are not applicable after each choice. Typically, the user will
select 2 to 4 filters and some operators, so 'normal' behaviour would be around
4 to 8 ajax calls. I want to fuzztest this component. The number of filters and
operations that I use in the fuzztest go up to 10, causing the OOM
> 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
