Re: [aspectj-users] Re: [NEWSDELIVER] Re: AJDT 1.3.1 makes Eclipserun ou

["Matt Chapman" <mpchapman@xxxxxxxxx>]

Is everyone who is experiencing these problems using WTP? There seems
to be several issues with the combination of AJDT + WTP at the moment.

Matt.

On 14/04/06, Adrian Sampaleanu <adrian.s@xxxxxxxxxxxx> wrote:
>
> I've also experienced significantly longer build times and very high memory
> use after changing a project to give it an aspect nature. There was only one
> simple aspect in the project whose pointcut did not match any joinpoints in
> the project classes (it was for patching a third party library).
>
> We were using Eclipse 3.2M6, AJDT 1.4.0.20060410070749, latest I build of
> WTP with max and starting heap set to 512MB (no permgen setting). After any
> save (we have about 1100 classes), it would take significantly longer than
> before (aspect nature) to build and memory would keep on growing to the max
> heap size, do a GC and drop to about 100MB or so and start climbing again -
> cycling like this several times. A colleague with the same configuration,
> actually got an OOM. After removing the aspect nature from the project,
> build times and memory use returned to normal.
>
>
>
>  ________________________________
>  From: aspectj-users-bounces@xxxxxxxxxxx
> [mailto:aspectj-users-bounces@xxxxxxxxxxx] On Behalf Of
> Ronald R. DiFrango
> Sent: Thursday, April 13, 2006 11:00 PM
> To: aspectj-users@xxxxxxxxxxx
> Subject: Re: [aspectj-users] Re: [NEWSDELIVER] Re: AJDT 1.3.1 makes
> Eclipserun out of memory
>
>
> All,
>
> I am experiencing this more frequently with the new build....that was
> suppose to fix this.
>
> Plus for me, if I do a clean and re-build it explodes.  My stats are some
> where north of what Alex notes below.
>
> Ron
>
>
> On 4/12/06, Alexandru Popescu
> <the.mindstorm.mailinglist@xxxxxxxxx> wrote:
> > I don't have a special setting for PermGen, but with my project which
> > is about 1300 classes (2 aspects with ITD weaved in about 20 classes),
> > during a clean rebuild the memory jumps from aprox.200M to over 512M.
> >
> > ./alex
> > --
> > .w( the_mindstorm )p.
> >
> >
> > On 4/12/06, Adrian Colyer <adrian.colyer@xxxxxxxxx > wrote:
> > > I've not been able to reproduce this, but.... I also got an OOM :
> PermGen
> > > space error yesterday. Noticeable because I've never seen a PermGen
> issue
> > > before when using Eclipse / AJDT. So I think there *is* something going
> on
> > > here that is beyond just Jeppe's local configuration.
> > >
> > > On 12/04/06, Jeppe Cramon <jeppe@xxxxxxxxx > wrote:
> > > >
> > > > Hi Andy
> > > >
> > > > It used work with previous AspectJ build (the ones that used more
> memory).
> > > >
> > > > I've been playing with around with JConsole and the issue seems to be
> > > > related Eclipse not using the vmargs it's feed using eclipse.ini,
> > > > eventhough it states so in the .log file.
> > > > I should have spotted it right away when it always bombed when the
> > > > heapsize reached 64 MB, but I was so focus on other causes for it.
> > > >
> > > > If I start Eclipse from the command line using java -Xms40m -Xmx756m
> > > > -XX:MaxPermSize=128m -jar startup.jar then I don't get any
> OutofMemory's.
> > > >
> > > > Here's the eclipse.ini that I use. Can you see the reason for Eclipse
> > > > not reading it properly?
> > > > -vmargs -Xms40m -Xmx756m -XX:MaxPermSize=128m
> > > >
> > > > /Jeppe
> > > >
> > > > Andy Clement wrote:
> > > > > Jeppe Cramon wrote:
> > > > >> I'm sorry to say it, but the same pattern has started showing with
> WTP
> > > > >> 1.5M5, Eclipse 3.2M6 and AJDT 1.4 and I really need help tracking
> down
> > > > >> the cause of this, as I'm completely unable to work with AspectJ
> (the
> > > > >> out of memory alway's happens during build).
> > > > >
> > > > > If you are running a 1.5 VM, you could try running with jconsole and
> > > > > seeing what the memory profile looks like for a build of the project
> -
> > > > > does all the memory definetly get used whilst building this WTP
> project?
> > > > > See:
> > >
> http://java.sun.com/developer/technicalArticles/J2SE/jconsole.html
> > > > >
> > > > > Are you able to close all the projects other than the WTP one so we
> can
> > > > > verify the WTP project is the problem?  is there anything in the
> AJDT
> > > > > event trace view that tells you what it is doing?
> > > > >
> > > > > I still can't quite tell from what you have said whether this set of
> > > > > projects has ever built reliably and consistently for a period of
> time
> > > > > whilst working with it in some previous version of AJDT?  Every
> single
> > > > > scenario I have tried with the latest AJDT has used at least 50%
> less
> > > > > memory than before.
> > > > >
> > > > > If it is still happening for that single project, are you able to
> > > > > exclude the aspects from the build of it (you won't be able to if
> they
> > > > > are critical to the thing building of course - eg. ITDs) - does it
> still
> > > > > fail?  Are you able to comment out 'parts' of that project and
> perhaps
> > > > > discover some 'feature' of the project that causes OOM ?
> > > > >
> > > > > if it has limited dependencies and is easy to set up, you could send
> it
> > > > > to us for investigation.
> > > > >
> > > > > Andy.
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > > --
> > > -- Adrian
> > >   adrian.colyer@xxxxxxxxx
> > > _______________________________________________
> > > aspectj-users mailing list
> > > aspectj-users@xxxxxxxxxxx
> > > https://dev.eclipse.org/mailman/listinfo/aspectj-users
> > >
> > >
> > >
> > _______________________________________________
> > aspectj-users mailing list
> > aspectj-users@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/aspectj-users
> >
>
>
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>
>
>