In working on a recent AspectJ bug, I have produced a modified weaver that is better behaved in terms of being available for GC once the classloader associated with it is dereferenced. I haven't put the changes into the AspectJ as I was hoping I could get a bit more testing done on it first. If anyone is doing loadtime weaving and wants to try it out, you can find it here:
http://www.eclipse.org/downloads/download.php?file=/tools/aspectj/dev/aspectjweaver_leakproof.jar If you do try it out and have any feedback, please add it to this bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=210470 Weaver instances won't use less memory (that is something else I'm working on) - but with these changes once the associated classloader is dereferenced, the weaver *should* vanish... thanks, Andy. _______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users
