On 09/27/2010 12:40 PM, Jonathan Costers wrote:
I think I identified the cause of the issue:
PreferredListgen, ClassDep and JarWrapper classes are executed during the
build, but the<java> task does not have the attribute "fork" set to "true".
The Ant documentation for<java> mentions that sometimes strange things can
happen without using fork=true ... So they recommend setting it if that
happens.
I tried doing that over the weekend, and let the build run for 200
consecutive times, using a bash script with a for loop.
I didn't see a single VM crash anymore.
Ah. Nice one! fork=true runs in separate VM, fork=false in the same as
ant. Thats a lot of state to carry with you! ;-)
Gr. Sim
