Eclipse segmentation fault

Question

I updated my ubuntu 14.04 and since then my eclipse is crashing. On Starting, it is giving segmentation fault as soon as i click the menu buttons or try to use any short-cut keys. I have tried most of workarounds, which i could find on internet. This is my eclipse.ini file contents

-startup plugins/org.eclipse.equinox.launcher_1.3.0.dist.jar      --launcher.GTK_version 2 --launcher.library plugins/org.eclipse.equinox.launcher.gtk.linux.x86_1.1.200.dist -showsplash org.eclipse.platform --launcher.XXMaxPermSize 256m --launcher.defaultAction openFile -vmargs -Xms40m -Xmx1024m -Dorg.eclipse.equinox.p2.reconciler.dropins.directory=/usr/share/eclipse/dropins -Dorg.eclipse.swt.browser.DefaultType=mozilla

I enable the core dump and checked using gdb, the stack seems to be corrupted. There is nothing i could find in /var/logs/system.log

If i remember it correctly, the update had to do something with some C++ libraries. Kindly help

Answer 1

we experienced the same problem within our company. The fix we implemented was to call java directly with -vm option.

Unknown why it solves it but I found it by accident when investigating the issue.

Open the eclipse.ini file and add the following directly after the openFile:

-vm 
/usr/bin/java 

That should resolve the issue.

Answer 2

Steps using grub: First, you must have it when starting the computer. If not, do this in the terminal:

sudo gedit /etc/default/grub

Now, change the line

GRUB_HIDDEN_TIMEOUT=0

to

#GRUB_HIDDEN_TIMEOUT=0

Then, update grub:

sudo update-grub

Check your actual kernel version:

uname -r

Now, you have grub when starting the machine. Restart the machine. A new black screen will appear with the grub options. Select the "advanced options". Then choose your previous linux-generic for booting.

Once booted, test your actual kernel version:

 uname -r

Now, try to start eclipse. Good luck!!

To remove the last update, for normal booting you must do

sudo apt-get purge linux-image-x.x.x linux-headers-x.x.x

Answer 3

Seems to be caused by an eclipse.ini setting like below:

-vm
/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/server/libjvm.so