ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hal Hildebrand \(web\)" <>
Subject Re: Memory problems?
Date Thu, 16 May 2002 18:27:38 GMT
We ran into this problem several times in our project and *no* amount of
memory allocation for the JVM would fix this.  None.

The *only* thing that worked was going through all our Ant scripts and
removing a lot of dependencies in the targets.  That was it.

Unfortunately, because of the complete lack of the stack trace, I never
did figure out what the problem really was.

But re-writing all the scripts to do things once, and not rely on so
many dependencies, was the only thing that truly worked.

I suspect it's some stack issue, but no -Xss parameter size worked for
this (I tried up to 1M).

It would *really* be nice if the VM would actually do a thread dump
(like when you do a kill -3, or ctrl-break) when this kind of thing
happened instead of the useless error it gives now.  <sigh>

----- Original Message -----
From: "Scott Ellsworth" <>

> On Thursday, May 16, 2002, at 09:15  AM, Duncan McNaught wrote:
> >     [javac] java.lang.OutOfMemoryError
> >     [javac]     <<no stack trace available>>
> set
>        memoryMaximumSize="${compile.memoryMaximumSize}"
> as an attribute in your javac task, with the property set to an
> appropriately large number like 128m.
> Scott
> --
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message