Looking through our tests, i found a test that rendered 50+ pages, in one method, without calling tester.destroy afterwards. Fixing that solved our problem and we now run 6.7.0. (Happily everafter:) Also, none of the other tests we had ran destroy!! Yes they do now!
Thanks for the hint about what could be causing this, it helped me find a bug in our tests. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/OOM-in-Tests-with-Wicket-6-7-0-tp4658111p4658218.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
