FYI, I have found in general that specifying "-vmargs -Xmx512MB -Xms256MB" has improved overall Eclipse compile and application performance, as well as, has eliminated a number of other strange problems/crashes within both Eclipse and WSAD 5. For those using WSAD running under the 1.4(1.3 too?) JDK, adding the "-server" option seems to also slightly improve performance. The machine I was using had 1GB ram, so it wasn't having problems due to a lack of overall memory -- anyone have any ideas why limiting the heap and stack might have helped?
> From: Federico Spinazzi <f.spinazzi@xxxxxxxxxxxxxx>
> Subject: Re: [aspectj] Re: [aspectj-users] out of memory during compilation in eclipse
> Sent: 21 Jan 2004 08:51:39
> Adrian Colyer wrote:
> > You need to add some startup arguments to the eclipse invocation (if
> > you're on windows, the easiest way to do this is create a shortcut to
> > eclipse.exe and then edit its properties). I use e.g.
> > xxx\eclipse-SDK-3.0M6-win32\eclipse\eclipse.exe -data <path to my
> > workspace dir> -vmargs -Xmx512M
> It fixed the problem.
> aspectj-users mailing list