Eclipse: Crash on loading

English Applications
1

Hi

I upgraded my system to 12.1 and now I can’t run eclipse anymore.

After the selection of workspace, eclipse crashes with following error message:

*** glibc detected *** /usr/bin/java: free(): invalid pointer: 0x0000000003124050 ***
======= Backtrace: =========
/lib64/libc.so.6(+0x74c06)[0x7fa55f0ffc06]
/usr/lib64/jvm/java-1.6.0-openjdk-1.6.0/jre/lib/amd64/server/libjvm.so(+0x4bbce8)[0x7fa55e762ce8]
/home/walterk/Downloads/eclipse/configuration/org.eclipse.osgi/bundles/351/1/.cp/libswt-pi-gtk-3738.so(Java_org_eclipse_swt_internal_gtk_OS__1g_1data_1input_1stream_1read_1line+0xe7)[0x7fa5520ddd10]
[0x7fa55a2efd68]
======= Memory map: ========
... and much more

I use Opensuse 12.1 64 bit with
eclipse-linuxtools-indigo-SR1-incubation-linux-gtk-x86_64
and
openjdk-1.6.0

Is this a bug or a misconfiguration on my side?

2

Found solution on another blog, hope it helps somebody else.

You have to export MALLOC_CHECK_=0 in the terminal you are launching eclipse

or start with a shortcut to “MALLOC_CHECK_=0 eclipse”

3

I have the exact same problem in OpenSuse 12.1/KDE. When I create a new project from a directory containing a large tree of C source files, eclipse starts in to work on the files and then poof! It goes away and does not come back. It does this wordlessly under KDE, of course that is probably because I am launching it from the desktop environment directly and not a knosole window. Sadly adding the MALLOC_CHECK=0 to the Exec= line in Eclipse.desktop (as well as in the Application menu) did not solve the problem. I may have to confine my use of eclipse to Windows via a shared drive, but I would rather get it working under Linux. Unfortunately, I am compelled to use this particular version of OpenSuse, and it appears incompatible. Any ideas?

4

Especially on a Dev machine, you should seriously consider upgrading to the latest OS and keep updating regularly.

By staying on 12.1, not only are you subject to no overall support you’re locked into using ancient libraries which may not be available on other machines today… So anything you build may or may not work once you start deploying.

Also, I highly doubt you’re going to run into the problems described in this thread whether you install Eclipse from the OSS or as a download from the Eclipse site if you’re running an updated openSUSE.

TSU