|
Re: 1.1.7 on 3.0M8 causes OutOfMemoryError [message #33686 is a reply to message #33606] |
Fri, 16 April 2004 07:28 |
Eclipse User |
|
|
|
Originally posted by: clemas.uk.ibm.com
How much memory do you normally run eclipse with? We normally work at
256Meg or sometimes even more
eclipse -vmargs -Xmx256M
overriding the standard 64M setup.
It would be useful to know:
- How many classes in your project (roughly)?
- How many aspects and how 'pervasive' they are across the codebase in
terms of crosscutting?
I've responded to Nedim's post about what he is seeing in the editor.
cheers,
Andy.
|
|
|
|
Re: 1.1.7 on 3.0M8 causes OutOfMemoryError [message #33910 is a reply to message #33747] |
Fri, 16 April 2004 08:54 |
Eclipse User |
|
|
|
Originally posted by: clemas.uk.ibm.com
479 classes and 1 aspect should not be a problem in a 256M eclipse.
Is there any way we can get hold of your code, if the Xmx change doesn't
fix it?
Michael Moser wrote:
> Is it enough to first remove the AspectJ nature, rebuild all, and
> then add again the AspectJ nature and rebuild again to get rid of any
> possibly corrupted remainings or do I really have to recreate the
> project from scratch?
Removing the nature, full build and adding the nature is probably
sufficient.
Andy.
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04275 seconds