[USDC-VT]

Any resolution to this? I have seem to be running into the same issue on Fedora 9 with MyEclipse 6.5…

[USDC-VT]

FWIW …..

Followed the thread here:

http://www.archivum.info/comp.lang.idl-pvwave/2008-07/msg00026.html

and renamed my /usr/lib/xulrunner-1.9 dir to /usr/lib/xulrunner-1.9.orig
started myeclipse — Started without the crash I have been seeing.
closed the ide
renamed the xulrunner dir back to original /usr/lib/xulrunner-1.9
restarted myeclipse and still did not experience the crash.

Bear in mind I have not actually DONE anything in the new myeclipse as yet —
i.e. have not even imported any projects or attempted to start a new project —
so could still be lurking issues.

oh, also launched via startup script which exports env var MOZILLA_FIVE_HOME=””

But at least I am now this far..

What an adventure.

[analogbytes]

Had the same problem with a fresh installation of MyEclipse 6.5 (Pulse Install) not loading past the Splash Screen. Always gave the following:

#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
#  SIGSEGV (0xb) at pc=0x02cb278c, pid=31756, tid=4159826128
#
# Java VM: Java HotSpot(TM) Server VM (1.5.0_11-b03 mixed mode)
# Problematic frame:
# C  [libxul.so+0xcb278c]
#
# An error report file with more information is saved as hs_err_pid31756.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#

After fighting this for hours trying different JDKs, versions of Eclipse, versions of MyEclipse, I finally ran across this posting. The renaming of the xulrunner-1.9 directory does the trick! However, upon renaming it back, MyEclipse will no longer start. Our shop only uses MyEclipse and I am trying to get a new computer ready for Monday with all the latest and greatest software/hardware, but it does not look good. Looks like I am going to have to install old software on a new computer to get it to work. I have seen that this bug has been around for a while. Whose bug is it, and why haven’t any decent workarounds been given since it does not appear that anyone is rushing to get this fix?

[benoitde]

I applied with success the workaround which is listed here:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=236724#c22

At least, it’s not necessary to rename the installed xulrunner directory (which breaks other things).

[Author]

Posts