In my experience AspectJ load-time weaving can significantly increase the memory requirements of a program, especially if you weave into every class in a system. Glassbox ships with slightly modified AspectJ that uses a lot less memory. See these bugs for more discussion: https://bugs.eclipse.org/bugs/show_bug.cgi?id=148773 https://bugs.eclipse.org/bugs/show_bug.cgi?id=166246
In essence, AspectJ head (and 1.5.3) keep a bytecode copy of every class every woven in memory to ensure consistent behavior should class GC evict a class. I think that's too high a price to pay for correctness. E.g., in a simple test I measured 300% total system memory overhead for that strategy versus evicting weaving state. HTH, Ron -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ramakrishnan Meenakshi Sundaram Sent: Monday, September 10, 2007 7:35 PM To: [email protected]; 'Eric Bodden'; 'Andy Clement' Subject: [aspectj-users] RE: Aspect java heap error Hi I had set the heap size with parameters -Xms64m -Xmx512m.Still I got the heap space error. Are LTW memory requirements so high? Are there any guidelines / online documents about this? Thanks in advance, Regards, Ramakrishnan _______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users _______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users
