axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran" <stev...@iseran.com>
Subject Re: Here are the options
Date Tue, 10 Sep 2002 21:19:24 GMT

----- Original Message -----
From: "Matt Seibert" <mseibert@us.ibm.com>

> So, we have to either make ANT smarter, or our process dumber.  Here is
> what I've got so far:
> ant clean compile buildTest   (java consumes 284 M of ram when you're
done)
>                         buildTest does a "samples" build when it builds
> test/functional (as a pre-req)
> ant all-tests                 (java consumes < 100 M of ram when you're
> done)
>                         This execs ONLY junit and functional-tests.  No
> compilations.....
>
> running this as two process commands "stops" ant between calls, and frees
> the memory that it is leaking.

I have a fix for ant that I'm just testing; if it looks on on ant and axis
tests then I'll commit it before the gump runs; it uses weak references to
stop tasks being cached. Of course, it assumes that I have identified the
cause of the leakage correctly...


Mime
View raw message