| 1.1.7 on 3.0M8 causes OutOfMemoryError [message #33606] |
Fri, 16 April 2004 02:58  |
Eclipse User |
|
|
|
I just installed the new "official" version 1.1.7 from the update
site.
Opening and rebuilding my project caused this:
Severity Description Resource In Folder Location Creation Time
2 Internal compiler error java.lang.OutOfMemoryError <class and
package-name here> April 16, 2004 8:50:07 AM
I am also observing some of the editor effects that Nedim desribes in
another thread
"Nedim Cholich" <nedim@codemonkeys.org> wrote in message
news:c5mtc6$55r$1@eclipse.org...
> Maybe I'm doing something wrong but AspectJ editor still doesn't
work! I
> completely removed previous version of AJDT and reinstalled using
update
> site.
> ...
though I only have no syntax highlighting, but otherwise the editing
seems normal.
I have to head off to a presentation now - I will continue my
experiments later...
Michael
|
|
|
|
|
|
|
| Re: 1.1.7 on 3.0M8 causes OutOfMemoryError [message #578041 is a reply to message #33606] |
Fri, 16 April 2004 03:28  |
| Eclipse User |
|
|
|
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 #578101 is a reply to message #33686] |
Fri, 16 April 2004 04:11 |
| Eclipse User |
|
|
|
"Andy Clement" <clemas@uk.ibm.com> wrote in message
news:c5o1ut$a1r$1@eclipse.org...
> 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.
I'll try that one. I also saw your other note and - of course :-) -
that was while 9re-)building a project that was still around from the
previous version.
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?
> It would be useful to know:
> - How many classes in your project (roughly)?
479 (including inner classes - I just counted the .class files in the
build subtree).
> - How many aspects and how 'pervasive' they are across the codebase
in
> terms of crosscutting?
Just one aspect which is crosscutting 6 classes (one "insertion" per
class). I am essentially just experimenting how we could modularize a
few seldom used features in our project, so that only people really
wanting them get code versions, that indeed contain these features
while others are not burdened (and slowed down) by them.
> I've responded to Nedim's post about what he is seeing in the
editor.
Thanks!
Michael
|
|
|
| Re: 1.1.7 on 3.0M8 causes OutOfMemoryError [message #578338 is a reply to message #33747] |
Fri, 16 April 2004 04:54 |
| Eclipse User |
|
|
|
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.03765 seconds
Home