Deepa Remesh wrote:
Thanks Kristian for trying this. I have not seen a mention of these OutOfMemoryErrors in any other thread. They seem to be happening only when running the entire suite of JUnit tests standalone. Running the JUnit tests as part of test harness does not have any problems.
Could it be because the old harness normally spawns a new JVM per test, contrary to a pure JUnit environment, where leftovers from some tests may eventually cause an OOME since all tests are run in the same JVM?
-- John
