Eclipse Community Forums: AspectJ » AJDT 1.3.1 makes Eclipse run out of memory

Search

Help

Login

Home » Language IDEs » AspectJ » AJDT 1.3.1 makes Eclipse run out of memory

Show: Today's Messages :: Show Polls :: Message Navigator

Switch to threaded view of this topic

Create a new topic

Submit Reply

AJDT 1.3.1 makes Eclipse run out of memory [message #64199]

Tue, 11 April 2006 10:55

Jeppe Cramon is currently offline

Friend

Messages: 37
Registered: July 2009

Member

After I upgraded to AJDT 1.3.1 my Eclipse 3.1.2 runs out of heap memory
during the first workspace build. I have 5 projects which have AspectJ
nature.

I'm using the following startup parameters (moved up from Xmx 512 with no
help): -vmargs -Xms40m -Xmx756m -XX:MaxPermSize=128m

I also tried without the MaxPermSize with the same result (just to be sure
it didn't have any effect).

/Jeppe

Report message to a moderator

Re: AJDT 1.3.1 makes Eclipse run out of memory [message #64242 is a reply to message #64199]

Tue, 11 April 2006 11:23

Andrew Clement is currently offline

Friend

Messages: 162
Registered: July 2009

Senior Member

Hi Jeppe,

I presume these projects compiled fine before upgrading to 1.3.1 ?

How large are these projects?

(We only test by changing Xmx, we don't bother with the other JVM runing
options for memory)

Andy.

Jeppe Cramon wrote:
> After I upgraded to AJDT 1.3.1 my Eclipse 3.1.2 runs out of heap memory
> during the first workspace build. I have 5 projects which have AspectJ
> nature.
>
> I'm using the following startup parameters (moved up from Xmx 512 with
> no help): -vmargs -Xms40m -Xmx756m -XX:MaxPermSize=128m
>
> I also tried without the MaxPermSize with the same result (just to be
> sure it didn't have any effect).
>
> /Jeppe
>

Report message to a moderator

Re: AJDT 1.3.1 makes Eclipse run out of memory [message #64264 is a reply to message #64199]

Tue, 11 April 2006 12:19

Jeppe Cramon is currently offline

Friend

Messages: 37
Registered: July 2009

Member

I've played around with it and it seems to be related to WTP

I've tried using 1.0.2 RC1
( http://download.eclipse.org/webtools/downloads/drops/R-1.0.2 RC1-200604070459/)
and two of the previous builds (the last of which I was using prior to
updating to AJDT 1.3.1) -
http://download.eclipse.org/webtools/downloads/drops/M-M2006 03280054-200603280054/
and
http://download.eclipse.org/webtools/downloads/drops/M-M2006 03230057-200603230057/

With 1.0.2 RC1 it runs out of memory immediately. Using either of two
older versions it takes longer before runs of memory.
It seems like AspectJ never finishes building the only WTP Web project in
my workspace (it simply gets stuck). After something trying to build it,
it simply runds out of memory.
The AJDT Event Trace didn't provide any information of value.

My colleague uses AJDT 1.3.1 with WTP 1.0.1 and doesn't have the same
problems.

/Jeppe

Report message to a moderator

Re: AJDT 1.3.1 makes Eclipse run out of memory [message #64284 is a reply to message #64242]

Tue, 11 April 2006 12:31

Jeppe Cramon is currently offline

Friend

Messages: 37
Registered: July 2009

Member

Hi Andy

In my workspace I have the following projects with AspectJ support enabled:
- 1 web project
- 4 Java projects
All in all we probably have roughly around 300 classes that are exposed to
weaving.

I have 5 aspects which all in all crosscut 52 classes.
The pointcuts are matching about 100 places.
50 out of the 100 are actually advised by Springs
AbstractTransactionAspect which means that they really result in 4 advises
coming into effect (before, after, after throwing, after returning advises)

/Jeppe

Report message to a moderator

Re: AJDT 1.3.1 makes Eclipse run out of memory [message #64307 is a reply to message #64264]

Tue, 11 April 2006 12:52

Eclipse User

Friend

Originally posted by: hawkinsh.uk.ibm.com

There was mention about a bug to do with WTP
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=130571) in another
newsgroup post:
http://www.eclipse.org/newsportal/article.php?id=1559&gr oup=eclipse.technology.ajdt#1559.
Maybe this is what you're running into?

Thanks, Helen

Report message to a moderator

Re: AJDT 1.3.1 makes Eclipse run out of memory [message #64328 is a reply to message #64307]

Tue, 11 April 2006 13:02

Jeppe Cramon is currently offline

Friend

Messages: 37
Registered: July 2009

Member

I don't think they're related. My problem seems to occur when AspectJ is
building the WTP Web project.

/Jeppe

Report message to a moderator

Re: AJDT 1.3.1 makes Eclipse run out of memory [message #64352 is a reply to message #64328]

Tue, 11 April 2006 16:15

Jeppe Cramon is currently offline

Friend

Messages: 37
Registered: July 2009

Member

I'm not sure what's wrong. I tried to use a collegaues working workspace
(which uses WTP 1.0.1 and AJDT 1.3.1) and try it on my machine without
any luck.
I then tried WTP 1.5M5, Eclipse 3.2M6 and AJDT 1.4 latest build and it
works without any problems, so I guess I'll stick with that solution and
give up on Eclipse 3.1.2, WTP 1.0.x and AJDT 1.3.1.

/Jeppe

Report message to a moderator

Re: AJDT 1.3.1 makes Eclipse run out of memory [message #64375 is a reply to message #64352]

Tue, 11 April 2006 21:57

Jeppe Cramon is currently offline

Friend

Messages: 37
Registered: July 2009

Member

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).

The .log file tells me that its running out of Permgen memory (using
arguments: -vmargs-Xms40m -Xmx756m):
!ENTRY org.eclipse.core.jobs 4 2 2006-04-11 23:32:12.015
!MESSAGE An internal error occurred during: "Processing Dirty Regions".
!STACK 0
java.lang.OutOfMemoryError: PermGen space

!ENTRY org.eclipse.ui 4 4 2006-04-11 23:32:12.015
!MESSAGE Unhandled event loop exception

!ENTRY org.eclipse.ui 4 0 2006-04-11 23:32:12.031
!MESSAGE PermGen space
!STACK 0
java.lang.OutOfMemoryError: PermGen space

!ENTRY org.eclipse.ui 4 4 2006-04-11 23:32:26.171
!MESSAGE Unhandled event loop exception

!ENTRY org.eclipse.ui 4 0 2006-04-11 23:32:27.562
!MESSAGE PermGen space
!STACK 0
java.lang.OutOfMemoryError: PermGen space

I then tried to change the Permgen space, but now it runs out of Heap
memory (a little later, I can now work around 2 minutes).
I use the following arguments -vmargs-Xms40m -Xmx756m -XX:MaxPermSize=128m
and at the time the OutOfMemory error appeared, the Eclipse memory
consumer said 63 of 64 MB Heap used.

..log content:

!ENTRY org.eclipse.ajdt.ui 4 0 2006-04-11 23:51:20.640
!MESSAGE OutOfMemoryError thrown: Java heap space
!STACK 0
java.lang.OutOfMemoryError: Java heap space

!ENTRY org.eclipse.core.resources 4 1 2006-04-11 23:51:33.484
!MESSAGE Internal Error
!STACK 0
java.lang.OutOfMemoryError: Java heap space

!ENTRY org.eclipse.ui 4 4 2006-04-11 23:51:37.984
!MESSAGE Unhandled event loop exception

!ENTRY org.eclipse.ui 4 0 2006-04-11 23:51:39.203
!MESSAGE Failed to execute runnable (java.lang.OutOfMemoryError: Java
heap space)

!ENTRY org.eclipse.core.jobs 4 2 2006-04-11 23:51:41.062
!MESSAGE An internal error occurred during: "Building workspace".
!STACK 0
java.lang.OutOfMemoryError: Java heap space

!ENTRY org.eclipse.core.jobs 4 2 2006-04-11 23:51:42.296
!MESSAGE An internal error occurred during: "Initializing Quick Diff".
!STACK 0
java.lang.OutOfMemoryError: Java heap space

Eclipse Environment info:
eclipse.buildId=I20060331-2000
java.version=1.5.0_06
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=da_DK

/Jeppe

Jeppe Cramon wrote:
> I'm not sure what's wrong. I tried to use a collegaues working workspace
> (which uses WTP 1.0.1 and AJDT 1.3.1) and try it on my machine without
> any luck.
> I then tried WTP 1.5M5, Eclipse 3.2M6 and AJDT 1.4 latest build and it
> works without any problems, so I guess I'll stick with that solution and
> give up on Eclipse 3.1.2, WTP 1.0.x and AJDT 1.3.1.
>
> /Jeppe

Report message to a moderator

Re: AJDT 1.3.1 makes Eclipse run out of memory [message #64398 is a reply to message #64375]

Wed, 12 April 2006 06:34

Andrew Clement is currently offline

Friend

Messages: 162
Registered: July 2009

Senior Member

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/jconsol e.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.

Report message to a moderator

Re: AJDT 1.3.1 makes Eclipse run out of memory [message #64421 is a reply to message #64398]

Wed, 12 April 2006 09:27

Jeppe Cramon is currently offline

Friend

Messages: 37
Registered: July 2009

Member

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/jconsol e.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.

Report message to a moderator

Re: AJDT 1.3.1 makes Eclipse run out of memory [message #593300 is a reply to message #64199]

Tue, 11 April 2006 11:23

Andrew Clement is currently offline

Friend

Messages: 162
Registered: July 2009

Senior Member

Hi Jeppe,

I presume these projects compiled fine before upgrading to 1.3.1 ?

How large are these projects?

(We only test by changing Xmx, we don't bother with the other JVM runing
options for memory)

Andy.

Jeppe Cramon wrote:
> After I upgraded to AJDT 1.3.1 my Eclipse 3.1.2 runs out of heap memory
> during the first workspace build. I have 5 projects which have AspectJ
> nature.
>
> I'm using the following startup parameters (moved up from Xmx 512 with
> no help): -vmargs -Xms40m -Xmx756m -XX:MaxPermSize=128m
>
> I also tried without the MaxPermSize with the same result (just to be
> sure it didn't have any effect).
>
> /Jeppe
>

Report message to a moderator

Re: AJDT 1.3.1 makes Eclipse run out of memory [message #593310 is a reply to message #64199]

Tue, 11 April 2006 12:19

Jeppe Cramon is currently offline

Friend

Messages: 37
Registered: July 2009

Member

I've played around with it and it seems to be related to WTP

I've tried using 1.0.2 RC1
( http://download.eclipse.org/webtools/downloads/drops/R-1.0.2 RC1-200604070459/)
and two of the previous builds (the last of which I was using prior to
updating to AJDT 1.3.1) -
http://download.eclipse.org/webtools/downloads/drops/M-M2006 03280054-200603280054/
and
http://download.eclipse.org/webtools/downloads/drops/M-M2006 03230057-200603230057/

With 1.0.2 RC1 it runs out of memory immediately. Using either of two
older versions it takes longer before runs of memory.
It seems like AspectJ never finishes building the only WTP Web project in
my workspace (it simply gets stuck). After something trying to build it,
it simply runds out of memory.
The AJDT Event Trace didn't provide any information of value.

My colleague uses AJDT 1.3.1 with WTP 1.0.1 and doesn't have the same
problems.

/Jeppe

Report message to a moderator

Re: AJDT 1.3.1 makes Eclipse run out of memory [message #593321 is a reply to message #64242]

Tue, 11 April 2006 12:31

Jeppe Cramon is currently offline

Friend

Messages: 37
Registered: July 2009

Member

Hi Andy

In my workspace I have the following projects with AspectJ support enabled:
- 1 web project
- 4 Java projects
All in all we probably have roughly around 300 classes that are exposed to
weaving.

I have 5 aspects which all in all crosscut 52 classes.
The pointcuts are matching about 100 places.
50 out of the 100 are actually advised by Springs
AbstractTransactionAspect which means that they really result in 4 advises
coming into effect (before, after, after throwing, after returning advises)

/Jeppe

Report message to a moderator

Re: AJDT 1.3.1 makes Eclipse run out of memory [message #593324 is a reply to message #64264]

Tue, 11 April 2006 12:52

Eclipse User

Friend

Originally posted by: hawkinsh.uk.ibm.com

There was mention about a bug to do with WTP
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=130571) in another
newsgroup post:
http://www.eclipse.org/newsportal/article.php?id=1559&gr oup=eclipse.technology.ajdt#1559
Maybe this is what you're running into?

Thanks, Helen

Report message to a moderator

Re: AJDT 1.3.1 makes Eclipse run out of memory [message #593335 is a reply to message #64307]

Tue, 11 April 2006 13:02

Jeppe Cramon is currently offline

Friend

Messages: 37
Registered: July 2009

Member

I don't think they're related. My problem seems to occur when AspectJ is
building the WTP Web project.

/Jeppe

Report message to a moderator

Re: AJDT 1.3.1 makes Eclipse run out of memory [message #593346 is a reply to message #64328]

Tue, 11 April 2006 16:15

Jeppe Cramon is currently offline

Friend

Messages: 37
Registered: July 2009

Member

I'm not sure what's wrong. I tried to use a collegaues working workspace
(which uses WTP 1.0.1 and AJDT 1.3.1) and try it on my machine without
any luck.
I then tried WTP 1.5M5, Eclipse 3.2M6 and AJDT 1.4 latest build and it
works without any problems, so I guess I'll stick with that solution and
give up on Eclipse 3.1.2, WTP 1.0.x and AJDT 1.3.1.

/Jeppe

Report message to a moderator

Re: AJDT 1.3.1 makes Eclipse run out of memory [message #593367 is a reply to message #64352]

Tue, 11 April 2006 21:57

Jeppe Cramon is currently offline

Friend

Messages: 37
Registered: July 2009

Member

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).

The .log file tells me that its running out of Permgen memory (using
arguments: -vmargs-Xms40m -Xmx756m):
!ENTRY org.eclipse.core.jobs 4 2 2006-04-11 23:32:12.015
!MESSAGE An internal error occurred during: "Processing Dirty Regions".
!STACK 0
java.lang.OutOfMemoryError: PermGen space

!ENTRY org.eclipse.ui 4 4 2006-04-11 23:32:12.015
!MESSAGE Unhandled event loop exception

!ENTRY org.eclipse.ui 4 0 2006-04-11 23:32:12.031
!MESSAGE PermGen space
!STACK 0
java.lang.OutOfMemoryError: PermGen space

!ENTRY org.eclipse.ui 4 4 2006-04-11 23:32:26.171
!MESSAGE Unhandled event loop exception

!ENTRY org.eclipse.ui 4 0 2006-04-11 23:32:27.562
!MESSAGE PermGen space
!STACK 0
java.lang.OutOfMemoryError: PermGen space

I then tried to change the Permgen space, but now it runs out of Heap
memory (a little later, I can now work around 2 minutes).
I use the following arguments -vmargs-Xms40m -Xmx756m -XX:MaxPermSize=128m
and at the time the OutOfMemory error appeared, the Eclipse memory
consumer said 63 of 64 MB Heap used.

..log content:

!ENTRY org.eclipse.ajdt.ui 4 0 2006-04-11 23:51:20.640
!MESSAGE OutOfMemoryError thrown: Java heap space
!STACK 0
java.lang.OutOfMemoryError: Java heap space

!ENTRY org.eclipse.core.resources 4 1 2006-04-11 23:51:33.484
!MESSAGE Internal Error
!STACK 0
java.lang.OutOfMemoryError: Java heap space

!ENTRY org.eclipse.ui 4 4 2006-04-11 23:51:37.984
!MESSAGE Unhandled event loop exception

!ENTRY org.eclipse.ui 4 0 2006-04-11 23:51:39.203
!MESSAGE Failed to execute runnable (java.lang.OutOfMemoryError: Java
heap space)

!ENTRY org.eclipse.core.jobs 4 2 2006-04-11 23:51:41.062
!MESSAGE An internal error occurred during: "Building workspace".
!STACK 0
java.lang.OutOfMemoryError: Java heap space

!ENTRY org.eclipse.core.jobs 4 2 2006-04-11 23:51:42.296
!MESSAGE An internal error occurred during: "Initializing Quick Diff".
!STACK 0
java.lang.OutOfMemoryError: Java heap space

Eclipse Environment info:
eclipse.buildId=I20060331-2000
java.version=1.5.0_06
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=da_DK

/Jeppe

Jeppe Cramon wrote:
> I'm not sure what's wrong. I tried to use a collegaues working workspace
> (which uses WTP 1.0.1 and AJDT 1.3.1) and try it on my machine without
> any luck.
> I then tried WTP 1.5M5, Eclipse 3.2M6 and AJDT 1.4 latest build and it
> works without any problems, so I guess I'll stick with that solution and
> give up on Eclipse 3.1.2, WTP 1.0.x and AJDT 1.3.1.
>
> /Jeppe

Report message to a moderator

Re: AJDT 1.3.1 makes Eclipse run out of memory [message #593382 is a reply to message #64375]

Wed, 12 April 2006 06:34

Andrew Clement is currently offline

Friend

Messages: 162
Registered: July 2009

Senior Member

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/jconsol e.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.

Report message to a moderator

Re: AJDT 1.3.1 makes Eclipse run out of memory [message #593396 is a reply to message #64398]

Wed, 12 April 2006 09:27

Jeppe Cramon is currently offline

Friend

Messages: 37
Registered: July 2009

Member

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/jconsol e.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.

Report message to a moderator

Switch to threaded view of this topic

Create a new topic

Submit Reply

Previous Topic:	AJDT 1.3.1 makes Eclipse run out of memory
Next Topic:	AspectJ 1.5.1a and Eclipse 3.0

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sat Nov 09 00:59:48 GMT 2024

Powered by FUDForum. Page generated in 0.07378 seconds

.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top