https://issues.apache.org/bugzilla/show_bug.cgi?id=41280
--- Comment #9 from Marek Slama <[EMAIL PROTECTED]> 2008-10-31 05:56:55 PST ---
Problem is that task does not fail when OutOfMemoryError happens in forked JVM.
Is it correct? It makes diagnostic difficult in case of building big project
https://issues.apache.org/bugzilla/show_bug.cgi?id=41280
--- Comment #8 from Marek Slama <[EMAIL PROTECTED]> 2008-10-31 05:49:29 PST ---
I used memoryMaximumSize="256m" for apt task and it works now. Yes warning
about forking is confusing and should be eliminated. Parent process memory
settin
https://issues.apache.org/bugzilla/show_bug.cgi?id=41280
--- Comment #7 from Steve Loughran <[EMAIL PROTECTED]> 2008-10-31 05:15:14 PST
---
looking at the source, that warning about forking is invalid; its the
superclass whining. The stack trace implies this is a new JVM (no ant classes
in t
https://issues.apache.org/bugzilla/show_bug.cgi?id=41280
--- Comment #6 from Marek Slama <[EMAIL PROTECTED]> 2008-10-31 04:48:57 PST ---
I set ANT_OPTS to "-Xmx1024m -Dbuild.compiler.debug=true" but it does not help
anyway. It would say this should be enough so there might be another problem
https://issues.apache.org/bugzilla/show_bug.cgi?id=41280
--- Comment #5 from Steve Loughran <[EMAIL PROTECTED]> 2008-10-31 04:21:29 PST
---
It probably only fails on a 64 bit VM because Sun 64-bit JVM heap requirements
are 1.5X 32 bit due entirely to memory pointer length; it probably works
https://issues.apache.org/bugzilla/show_bug.cgi?id=41280
--- Comment #4 from Marek Slama <[EMAIL PROTECTED]> 2008-10-31 03:20:54 PST ---
I forgot to say: The same target passes on 32bit JDK.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
--- You are re
https://issues.apache.org/bugzilla/show_bug.cgi?id=41280
Marek Slama <[EMAIL PROTECTED]> changed:
What|Removed |Added
CC||[EMAIL PROTECTED]
