Hi Florian, Just want to double check:
> I've tried minmalModel=true and also typeDemotion=true. Is that an email typo or did you mispell minimalModel=true in the project settings too? Right now you have to set those properties for all projects, I presume you are doing that, and not just for one. (I think there might be a system property you can set when you start your eclipse so it applies the settings across all projects, but I'd have to check) -Xset:minimalModel=true,typeDemotion=true They definitely should not have zero impact, they may not fix things but at least something should happen: heap coming down, compile time going up, something. There is a debug option I think we can turn on to confirm they are active, you may even see something if you start eclipse with the console open (-consolelog option). My suspicion on heap usage is usually the structure model. The 'minimalModel' setting should ensure it discards model elements for any types not affected by aspects - so its impact can depend on how pervasive your aspects are. You only have a few, but do they hit most of the files in most of the projects? cheers Andy On 27 January 2011 06:35, Florian Weiss <florian.we...@qnamic.com> wrote: > Hi @ all > > > > I have a problem using AspectJ within Eclipse (AJDT). > > > > Problem description: > > Following project dependencies. > > > > Project1 > > | > > Project2 > > / \ > > Project3 Project4 > > / | \ / > > Project5 | Project6 > > Project7 > > > > (aprox. 10K Classes, 10 Aspects) > > > > All Projects are AJ projects. The aspects are located in Project1 and 3 and > should be woven into all projects that depend directly or indirectly on the > containing project. > > > > All projects have a project dependency to the project(s) above. And also an > entry in the aspect path to the bin folder of the project(s) above. Both > dependencies are exported. > > I might be wrong but AFAIK this should be correct. > > > > Most of the pointcuts use execution() compared with within(). There are only > few that user call(). > > > > The problem is that the build fails since it runs out of heap space and > Eclipse crashes(Heap size is set to 3 GB). I've tried minmalModel=true and > also typeDemotion=true. No changes. > > > > Environment Info: > > Eclipse 3.6.1 (Helios) > > WinXP Pro SP2 running as a VM > > 10 GB RAM > > > > Any ideas what could be wrong with this setup that causes this excessive use > of heap? > > > > If some important information is missing please tell. > > > > Greets Florian > > > > _______________________________________________ > aspectj-users mailing list > aspectj-users@eclipse.org > https://dev.eclipse.org/mailman/listinfo/aspectj-users > > _______________________________________________ aspectj-users mailing list aspectj-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/aspectj-users
