Return-Path: Delivered-To: apmail-jakarta-ant-user-archive@apache.org Received: (qmail 8094 invoked from network); 13 Aug 2002 19:02:38 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 13 Aug 2002 19:02:38 -0000 Received: (qmail 29393 invoked by uid 97); 13 Aug 2002 19:02:17 -0000 Delivered-To: qmlist-jakarta-archive-ant-user@jakarta.apache.org Received: (qmail 29382 invoked by uid 97); 13 Aug 2002 19:02:17 -0000 Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Users List" Reply-To: "Ant Users List" Delivered-To: mailing list ant-user@jakarta.apache.org Received: (qmail 2983 invoked by uid 98); 10 Aug 2002 14:41:58 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Message-Id: <5.0.0.25.2.20020810103144.00ac8600@camail2.harvard.edu> X-Sender: Brobinso@camail2.harvard.edu X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Sat, 10 Aug 2002 10:39:54 -0400 To: ant-user@jakarta.apache.org From: Brian Robinson Subject: RE: Out of memory issues when compiling Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I'm getting the same "out of memory error" as described below on compiles, but when I tried form="yes" memoryInitialSize="128m" memoryMaximumSize="512m" I got the message: Class org.apache.tools.ant.taskdefs.Javac doesn't support the "fork" attribute then when I took out the fork attribute I got: Class org.apache.tools.ant.taskdefs.Javac doesn't support the "memoryinitialsize" attribute when I got rid of the fork line Any obvious clues on how to overcome this? -brian --------------------------------------------------------------------------------------------------- Seems like you covered most bases... I'd try with: ... since you have 1GB RAM. We compile with mostly 2 , one with 1400 classes and the other with 1800 classes with the settings above, and we used to compile it in one pass only. We're now trying to move away from such a monolithic architecture, and have refactored quite a bit to better define more independent layers that can be compiled independently (in the right order). Using precompiled layers that the currently compiled layer depends on makes compilation lighter on the memory side, and development easier overall (separating the layers into there own sub-project). The challenge is to go from a monolithic to a layered architecture... --DD -----Original Message----- From: Ed Mangual [mailto:ed.mangual@s1.com] Sent: Tuesday, July 30, 2002 3:46 PM To: 'ant-user@jakarta.apache.org' Subject: Out of memory issues when compiling I am compiling a fairly large project containing anywhere from 1500 to 2500 source files and I am constantly getting the compiler has ran out memory error. I have tried using the "set ANT_OPTS=-Xmx512m" in the ant batch file, forking the javac processes and even setting the memoryInitialSize and memoryMaximumSize, but nothing seems to work. I am compiling on a dual 1gig xeon on win2k, Ant-1.4.1, sun jdk 1.2.2_12 and with 1GB of memory. I run into the same problem using Ant 1.5. I have watched the java process used by Ant and it seems to grow with each task it executes with out releasing the memory, it looks to me that when I forked the process it helped some but I still see the errors. Any ideas? Do we have some type of memory leak? Ed Mangual -- To unsubscribe, e-mail: For additional commands, e-mail: