[Tony Herstell]

Got M2 and it updated; now I get memory issues and no MyEclipse burst page when it loads.

After short while a dialog box pops up telling me to run with some other options for larger memory.

Never had to do this before (I assume MyEclipse sets these for me).

Any ideas?… I have had this before and ended up just downloading a complete installer again.

WinXP64.

[Loyal Water]

Can you go to MyEclipse > Installation Summary > Installation Details and paste the information here for me.

Also, can you paste the entire error message here for me.

[Tony Herstell]

Installation root:
C:\Program Files (x86)\MyEclipse 7.0 M2

*** Date:
Tuesday, 30 September 2008 12:21:09 AM NZST

** System properties:
OS=Windows2003
OS version=5.2.0
Java version=1.5.0_11

*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 7.0 Milestone-2
Build id: 7.0-M2-20080915

*** Eclipse details:
Eclipse SDK

Version: 3.4.1
Build id: M20080911-1700

Eclipse Project SDK

Version: 3.4.1.R34x_v20080827-7O7S78C2J40sK2o_ALcK8tLN_yZSJeg0P-3EtL4Ra90kv
Build id: M20080911-1700

Eclipse Platform

Version: 3.4.1.r341_v20080731-9I96EiDElYevwz-p1bP5z-NlAaP7vtX6Utotqsu
Build id: M20080911-1700

Eclipse Java Development Tools

Version: 3.4.1.r341_v20080709-0800-7o7tEAfEF_U5qyUgrb2HAp539P97
Build id: M20080709-0800

Eclipse Graphical Editing Framework GEF

Version: 3.4.0.v20080115-677-8082A5696H274A
Build id: 200806091334

Eclipse RCP

Version: 3.4.100.r341_v20080814-989JESIEdAciFYfkZZsBfSwQ2341
Build id: I20080617-2000

Eclipse Plug-in Development Environment

Version: 3.4.1.r341_v20080731-7T7U0E9mlRIuGUYviF_VP
Build id: I20080617-2000

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\Program Files (x86)\MyEclipse 7.0 M2\eclipse\eclipse.exe
-name
Eclipse
–launcher.library
C:\Program Files (x86)\MyEclipse 7.0 M2\eclipse\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.101.R34x_v20080731\eclipse_1115.dll
-startup
C:\Program Files (x86)\MyEclipse 7.0 M2\eclipse\plugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20080819.jar
-exitdata
16b4_74
com.genuitec.myeclipse.product
-clean
-vm
C:\Program Files (x86)\MyEclipse 7.0 M2\jre\bin\javaw.exe

[Loyal Water]

Also, can you paste the entire error message here for me.

[Tony Herstell]

It just says run eclipse with -Xblah blah ..
You cant copy/paste the contents of the window (which is not very useful).

Ill just download a complete 200MB new install file as this usually fixes the problem… its the updates that cause the problem when the launcher seems to revert to eclipse launcher as apposed to myeclipse launcher.

[Loyal Water]

Do you have the memory arguments in your eclipse.ini file? I guess you should refer to this thread:-
https://www.genuitec.com/forums/topic/troubleshoot-getting-outofmemoryexceptions-2/

[Tony Herstell]

@support-nipun wrote:

Do you have the memory arguments in your eclipse.ini file? I guess you should refer to this thread:-
https://www.genuitec.com/forums/topic/troubleshoot-getting-outofmemoryexceptions-2/

I will try tonight.

Never <b>EVER</b> altered the .ini file before M2 and been using MyEclipse for years.

I use a PC is this .ini a Mac only thing?

No idea where it is but will find it and try.

[Tony Herstell]

Still horribly unstable.

I have put this:

-vmargs -Xms128M -Xmx512M -XX:PermSize=64M -XX:MaxPermSize=128M

in every place I can find.

Please can you list where it should be put… then I can be sure I hit the right place.

Dev = Win XP 64 Pro.

[Riyad Kalla]

Few things I’m seeing here that perked my ears up…

1. The eclipse.ini file is in the <ME Install Dir>\eclipse directory, there should have already been those arguments in the file and they have to be 1 per line, for example, your eclipse.ini would normally look something like this

-clean
-showsplash
com.genuitec.myeclipse.product.ide
--launcher.XXMaxPermSize
256m
-vmargs
-Xms128m
-Xmx512m
-Duser.language=en 
-XX:PermSize=128M 
-XX:MaxPermSize=256M

Please remove any duplicate flags that you may have copied those arguments around to, it’s possible they may invalid loading of the legit arguments in the eclipse.ini file; you can also try editing your eclipse.ini to look like what I just pasted there.

Also, the full MyEclipse installer is around 650mb, when you mentioned 200mb, I immediately thought of a incomplete download.

Let’s get the memory arguments squared away them move onto other verification steps.

[Tony Herstell]

This is what was in the .ini file (from a clean install and update)

com.genuitec.myeclipse.product
-startup
plugins\org.eclipse.equinox.launcher_1.0.101.R34x_v20080819.jar
--launcher.library
plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.101.R34x_v20080731
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
-clean
-vmargs
-Xmx512m
-Xms40m
-Xmx256m

I have replaced with your setup and will report back if its more stable.

[Tony Herstell]

No branding with old config.ini
If you have an old config.ini file and use it with a new Eclipse build, you may not get the correct product branding. This is because the id of the standard Eclipse product changed. Users in shared install scenarios may end up in this situation as previous builds of Eclipse automatically generated config.ini files in some cases. The work around is either to delete the local config.ini or update the eclipse.product line to read eclipse.product=org.eclipse.platform.ide.

I tried changing this and got no MyEclipse branding (on the burst screen at least) and when I deletd the file MyEclipse would not run up:

!SESSION 2008-11-26 09:18:45.250 -----------------------------------------------
eclipse.buildId=unknown
java.version=1.5.0_11
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_NZ
Command-line arguments:  -os win32 -ws win32 -arch x86 -clean

!ENTRY org.eclipse.osgi 4 0 2008-11-26 09:18:45.765
!MESSAGE Application error
!STACK 1
java.lang.IllegalStateException: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolved and started (see config.ini).
    at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:74)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:386)
    at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549)
    at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504)
    at org.eclipse.equinox.launcher.Main.run(Main.java:1236)
    at org.eclipse.equinox.launcher.Main.main(Main.java:1212)

[Riyad Kalla]

I’m not clear from your message if you erased the eclipse.ini file or not or where we stand… I saw your first post that you would report back, then your 2nd post that you erased the file and now ME won’t run.

So my gut reaction is to have you put the eclipse.ini file back in place and go back to the original statement of reporting back if the dialed up memory arguments helped.

Please clarify if I’m misunderstanding you.

[Author]

Posts