On 2009-10-06, Knuplesch, Juergen <juergen.knuple...@icongmbh.de> wrote:
> Hello, > Thanks for your answer! > Good to know, that there are known problems. Unfortunately they may not be. > I already fork the junit tests. Then the change I pointed at won't affect you since the classloader leak only applies to non-forked tests. > Memory eater is also junitreport (especially for 2200 tests) etc., Ouch. I don't think we have any means to address that. > all the XSLT stuff needs a lot of memory that should be eligible to be garbage collected once the task are done. If you had any way to attach a memory profiler to it so we could see what is occupying the memory, that would be great. > and of course Tasks like jar. which shouldn't keep too much memory around once it is done either. > So I have to wait for Ant 1.7.2 or create one out of the trunk... That would be 1.8.0 and I'm afraid it wouldn't help. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@ant.apache.org For additional commands, e-mail: user-h...@ant.apache.org
