> -----Original Message----- > From: Nick Reeves [mailto:[EMAIL PROTECTED] > Sent: Friday, January 19, 2001 4:43 AM > To: '[EMAIL PROTECTED]' > Subject: Object retention problem with javac > > I noticed the memory usage of my Ant tasks was growing large so I ran Ant > with the Heap analysis tool and got the follow results. > ... snip ... > > The problem with this is that since javac runs in the same JVM it > holds onto > 4 objects (Hashtable entry, Identifier, String, char array) for > every unique > Java language identifer ever seen since the build started. > > Solution proposed: run calls to javac inside their own ClassLoader > > Comments ? >
Just a thought: A potential quick fix could be to run javac in it's on JVM. Something like a 'fork' attribute on the <java> task. Josh Davis [EMAIL PROTECTED]
