Hi Charlie, Actually, I continued to see that issue so I double checked and actually it's something to do with me using JDK7 build 32 (because of an AWT bug sucking a lot in Netbeans on my Ubuntu actually). Switching back to Java 1.6 or 1.5 fixes the issue. Strange because that's very precisely right after your commit that the apt task started to generate an out of mem error. I had no issue before, even with that JDK7.
Also fixing the memory usage for the apt task doesn't sound as trivial as for a javac task. The only input I saw was there: http://mail-archives.apache.org/mod_mbox/ant-dev/200701.mbox/[EMAIL PROTECTED]/bugzilla/%3E Meaning hacking directly inside the apt Java task definition to provide more memory... Not really a Friday evening job... So I just compiled using a previous Java and that was it. Thank you any way for you time and sorry again for the wrong report. Raphaël Valyi. On Wed, Aug 6, 2008 at 2:38 AM, Charles Oliver Nutter <[EMAIL PROTECTED]> wrote: > Raphaël Valyi wrote: >> >> guys, for me commit #7376 is making ant jar to leak and fail to >> complete in the apt annotation phase >> stack trace here: > > Only thing I could think of is that we hit our upper memory limit for javac > process. Can you try tweaking that in the build and see if it fixes it for > you? That commit didn't touch *any* code that could possibly cause this. > > - Charlie > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
