ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 40249] - Out of Memory exceptions are near impossible to find the source of.
Date Tue, 15 Aug 2006 13:10:16 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=40249>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=40249





------- Additional Comments From ryan@thebookhauler.com  2006-08-15 13:10 -------
I don't have any custom tasks and my build file is 600 lines long (although all
of the targets that got executed were all within a 140 line block).  I'm using
-Xmx512M (on a machine with only 1GB of physical ram, although plenty of virtual
memory).  

The last line number in the ant version of the stack trace shows the antcall to
the target that had the actual exception.  After using echos to figure out where
the build was really failing, it turns out that it was when I was using the
replace task on an 86 MB file. I was trying to rebuild my development database.
 The only tasks I called before the replace were sql, mkdir, copy, echo and
property. 

I managed to get around this by using -Xmx1024M which is a little rediculous,
but hey - a guy's got deadlines.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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


Mime
View raw message