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 Sat, 19 Aug 2006 21:43:15 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 stevel@apache.org  2006-08-19 21:43 -------
Hey, its ok to be pissed off with tool that dont work right. Why else would new
ones be written.

Presumably the problem is we cannot create a new BuildException with stack trace.

options
 -catch OOME and handle by printing out current fault, saying set ANT_OPTS to
-XX whatever

 -preallocate an emergency buffer and delete all references to it then force a
system.gc before creating a buildexception.

I've not done the latter on a java app, though it takes me back to some C++
emergency heap management code. Its a dog to test.

-- 
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