Mailing-List: contact dev-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Ant Developers List" <dev@ant.apache.org>
Received-SPF: neutral (herse.apache.org: local policy)
Message-ID: <467AA7ED.9000606@apache.org>
Date: Thu, 21 Jun 2007 17:31:41 +0100
From: Steve Loughran <stevel@apache.org>
User-Agent: Thunderbird 1.5.0.10 (X11/20070221)
MIME-Version: 1.0
To: Ant Developers List <dev@ant.apache.org>
Subject: OOmemory, ant1.7, java1.5+, windows only
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


the big smartfrog build is suddenly oom-ing, on windows only, more often 
on java1.6 but now on java1.5 too.

we're using ivy to choreograph, running threads for functional testing. 
javac, rmic, junit, all are set to fork, but still we run out of memory 
after about 40 minutes into the full build/test. All is well on unix, 
but not windows.

Anyone got any ideas? What's the best way to debug this? I've never 
profiled a build before. We could maybe have a new listener that prints 
out memory/heap space status as it exits projects, a profiling 
listener...then there is the profilers under netbeans and the 
java1.5/1.6 memory tools.

-steve

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org