is anybody investigating the blatant memory leaking issues with the antcall
target?
-----Original Message-----
From: Murray, Mike B. [mailto:mbm@ptc.com]
Sent: Tuesday, November 05, 2002 4:31 PM
To: Ant Users List
Subject: RE: ant.system.gc()?
I'm using 1.5.1, and my build was running out of memory without any javac
invocations. All together, it would have made about 75 Ant and/or AntCall
invocations. I had to break it up and call it from a batch file to avoid
the memory problems. Not a pleasing solution by any means.
Mike
-----Original Message-----
From: Steve Loughran [mailto:steve_l@iseran.com]
Sent: Tuesday, November 05, 2002 3:01 PM
To: Ant Users List
Subject: Re: ant.system.gc()?
----- Original Message -----
From: "David McTavish" <dmctavish@SANDVINE.com>
To: "'Ant Users List'" <ant-user@jakarta.apache.org>
Sent: Tuesday, November 05, 2002 12:25 PM
Subject: ant.system.gc()?
> Is there anyway to tell ant to run the garbage collection? I have a
> fairly complicated build script that must execute peer projects so
> that it can properly import the dependent libraries. What is
> happening, is that every peer build process that is called stays in
> memory until the entire build process is complete. This results in an
> ever-increasing JVM, until the point that the JVM throws an
> OutOfMemoryError. (This is occuring at about 80MB). I COULD set the
> upper limit higher, but it seems a little ridiculous that ant takes 80
> MB to compile the source.
This is more likely a memory leak than anything else.
-use java1.4 or fork javac (it leaked in 1.3)
-use ant1.5.1 that fixes leaks related to <ant>
--
To unsubscribe, e-mail: <mailto:ant-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-user-help@jakarta.apache.org>
--
To unsubscribe, e-mail: <mailto:ant-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:ant-user-help@jakarta.apache.org>
|