Using AntClassLoader just caused the build to block consuming no CPU mysteriously.
I also no longer suspect javac as being the cause of the memory bloat as the build seemed to take just as much memory as before. So although javac has a (minor ?) object retention problems it wasn't the cause of my problem. I must have taken my heap snapshot too late. I'm not planning to follow this up. > -----Original Message----- > From: Nick Reeves [mailto:[EMAIL PROTECTED] > Sent: 19 January 2001 12:54 > To: '[EMAIL PROTECTED]' > Subject: RE: Object retention problem with javac > > > Will try AntClassLoader and let you know. > > > -----Original Message----- > > From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > > Sent: 19 January 2001 12:47 > > To: [EMAIL PROTECTED] > > Subject: Re: Object retention problem with javac > > > > > > Nick Reeves <[EMAIL PROTECTED]> wrote: > > > > > Solution proposed: run calls to javac inside their own ClassLoader > > > > I'm not sure this would work and not cause a load of classloader > > problems (ClassCastExceptions you usually get for classes loaded via > > different loaders) but sure worth a try. > > > > A start would be to modify one of the Javac?? classes in the > > .../taskdefs/compilers directory to load the compiler class via an > > AntClassLoader instance. Could you give it a try and report back to > > us? > > > > Stefan > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
