[Michael Stacey]

I am trying to use the newest version and Eclipse is crashing 5+ times during my day.
Most often, it happens when opening a project, but not exclusively. Let me know what other info you need; my subscription renewal is coming up…

*** Date: Thursday, February 19, 2009 2:21:32 PM ET

*** Platform Details:

*** System properties:
com.genuitec.pulse.client.basedir.location.override=/home/mstacey/Pulse
com.genuitec.pulse.client.blueprint.id=rmb-38090
com.genuitec.pulse.client.credentials=cIpsIJkYfnuaaYrhYeumOC0+CfqdP74O/KwRD1sV26IrFvWsSteYPpQmF2J+Z8zXHQw2UcOUX6vM 1Vb6WWIRVQSkmOGWxrZC/IfdYUQRvEDg/YiMF9JNu22SAncdaF1jgJo5nRk7bHkwbVdEkTXPeRdu jXGn5sREYHPTy16cMU4=
com.genuitec.pulse.client.handshake.id=c55953ea-fe94-414d-b886-69134a583524
com.genuitec.pulse.client.rcb.id=37963
com.genuitec.pulse.common.server.url=https://www.poweredbypulse.com:443
eclipse.commands=-os
linux
-ws
gtk
-arch
x86
-showsplash
-launcher
/home/mstacey/Pulse/MyEclipse 7.0/myeclipse
-name
Myeclipse

[Loyal Water]

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

[Michael Stacey]

*** Date:
Friday, February 20, 2009 6:42:48 AM EST

** System properties:
OS=Linux
OS version=2.6.9.0
Java version=1.5.0_11

*** MyEclipse details:
MyEclipse Enterprise Workbench
Version: 7.0
Build id: 7.0-20081201

*** Eclipse details:
MyEclipse Enterprise Workbench

Version: 7.0
Build id: 7.0-20081201

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.1.v20080806-67718083A56B4H2A3213573
Build id: 200809101400

Eclipse RCP

Version: 3.4.100.r341_v20080814-989JESIEdAciFYfkZZsBfSwQ2341
Build id: M20080703-0800

Eclipse Plug-in Development Environment

Version: 3.4.1.r341_v20080731-7T7U0E9mlRIuGUYviF_VP
Build id: M20080703-0800

Eclipse startup command=-os
linux
-ws
gtk
-arch
x86
-showsplash
-launcher
/home/mstacey/Pulse/MyEclipse 7.0/myeclipse
-name
Myeclipse
–launcher.library
/home/mstacey/Pulse/MyEclipse 7.0//../Common/plugins/org.eclipse.equinox.launcher.gtk.linux.x86_1.0.101.R34x_v20080805/eclipse_1115.so
-startup
/home/mstacey/Pulse/MyEclipse 7.0//../Common/plugins/org.eclipse.equinox.launcher_1.0.101.R34x_v20080819.jar
-exitdata
1230012
-clean
-configuration
/home/mstacey/Pulse/MyEclipse 7.0/configuration
-vm
/home/mstacey/Pulse/Common/binary/com.sun.java.jre.linux.x86_1.5.0.011/bin/java

[Riyad Kalla]

Stacey, what does “uname -a” report from the command line? It’s possible there is some native-component conflict occuring between SWT and GTK on your system.

Also when MyEclipse crashes, what happens… do you get a VM Crash dialog explaining the command lines that were used? Does it just segfault and disappear? Something else happen? Please describe what “crash” means here.

[Michael Stacey]

uname -a
Linux koa-2.lexi.com 2.6.9-78.0.8.ELsmp #1 SMP Wed Nov 19 20:05:04 EST 2008 i686 i686 i386 GNU/Linux

The “crash” means it just disappears; no dialog.

[Riyad Kalla]

Ugg, that sounds like a GTK/SWT/VM platform conflict if it’s straight out segfaulting like that.

You *can* try adjusting the JRE that launches MyEclipse by installing a 1.6.0 VM, and going into the MyEclipse install dir and adjusting the -vm argument to point directly at that 1.6 “java” executable… in some cases this has helped. Another alternative that I’ve seen help is making sure your GTK libs are up to date.

[Michael Stacey]

GTK libs are completely up to date.
So MyEclipse requires jdk 1.6 now?

[Michael Stacey]

Shouldn’t Pulse handle the installation of the correct JDK? Changing to 1.6 caused even more problems.

[Michael Stacey]

So is this issue dead?

[Michael Stacey]

been almost a week…

[Riyad Kalla]

Sorry about that, this is sitting on my desk and got buried — no MyEclipse doesn’t require JDK 6, it was just a suggestion as it’s helped some folks in the past on Linux due to the native-component integration and I thought it might help.

Try opening up your myeclipse.ini file that is installed along side MyEclipse’s executable and dialing up the permgen space to 256m and see if the behavior improved. Go to Window > Prefs > General > “Show heap space status” and see if you can pin-point certain behaviors that blow the heap space out of the water most likely resulting in the crashing doom.

Also just to make sure, when you grabbed Java 6, make sure it’s the Sun VM from java.sun.com — we don’t test IBM’s JDK or the OpenJDK (or GCJ).

[Author]

Posts