You are not logged in.
Ever since my last system update eclipse crashes for no apparent reason.
I have determined that it is not due to lack of memory, because the heap status in eclipse always shows that memory is available when eclipse crashes.
I have Eclipse 4.3.2 installed via pacman. And jdk7-openjdk, jre7-openjdk and jre7-openjdk-headless also installed via pacman. (This setup was working perfectly until a few days ago)
This is my /usr/share/eclipse/eclipse.ini
-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20140116-2212
-product
org.eclipse.epp.package.standard.product
--launcher.defaultAction
openFile
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
--launcher.appendVmargs
-vmargs
-Dosgi.requiredJavaVersion=1.6
-XX:MaxPermSize=512m
-Xms512m
-Xmx1024mThis is a log (workspace/.metadata/.log) when the eclipse crashed:
!SESSION 2014-03-28 18:42:31.757 -----------------------------------------------
eclipse.buildId=4.3.2.M20140221-1700
java.version=1.7.0_51
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=pt_PT
Framework arguments: -product org.eclipse.epp.package.standard.product
Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.standard.product
!ENTRY org.eclipse.m2e.logback.appender 2 0 2014-03-28 18:43:05.707
!MESSAGE CatalogItem org.eclipse.m2e.discovery.lifecyclemapping.m2e-egit does not contain lifecycle mapping metadata
!ENTRY org.eclipse.m2e.logback.appender 2 0 2014-03-28 18:43:05.711
!MESSAGE CatalogItem org.eclipse.m2e.discovery.lifecyclemapping.m2e-subversive does not contain lifecycle mapping metadata
!ENTRY org.eclipse.m2e.logback.appender 2 0 2014-03-28 18:43:05.713
!MESSAGE CatalogItem org.eclipse.m2e.discovery.lifecyclemapping.m2e-subclipse does not contain lifecycle mapping metadata
!ENTRY org.eclipse.m2e.logback.appender 2 0 2014-03-28 18:43:17.747
!MESSAGE Using platform encoding (UTF-8 actually) to copy filtered resources, i.e. build is platform dependent!
(this message about UTF-8 is repeated some more times, removed for clarity)
!ENTRY org.eclipse.m2e.logback.appender 2 0 2014-03-28 18:44:11.844
!MESSAGE Using platform encoding (UTF-8 actually) to copy filtered resources, i.e. build is platform dependent!This is a log returned by running
$ /usr/share/eclipse/eclipse -clean -consoleLog -debugStart VM: /usr/bin/java
-Dosgi.requiredJavaVersion=1.6
-XX:MaxPermSize=512m
-Xms512m
-Xmx1024m
-jar /usr/share/eclipse//plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
-os linux
-ws gtk
-arch x86_64
-showsplash /usr/share/eclipse//plugins/org.eclipse.platform_4.3.2.v20140221-1700/splash.bmp
-launcher /usr/share/eclipse/eclipse
-name Eclipse
--launcher.library /usr/share/eclipse//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20140116-2212/eclipse_1508.so
-startup /usr/share/eclipse//plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
--launcher.appendVmargs
-exitdata 7c002a
-product org.eclipse.epp.package.standard.product
-clean
-consoleLog
-debug
-vm /usr/bin/java
-vmargs
-Dosgi.requiredJavaVersion=1.6
-XX:MaxPermSize=512m
-Xms512m
-Xmx1024m
-jar /usr/share/eclipse//plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar
Install location:
file:/usr/share/eclipse/
Configuration file:
file:/usr/share/eclipse/configuration/config.ini loaded
Configuration location:
file:/home/simao/.eclipse/org.eclipse.platform_4.3.2_1543616141_linux_gtk_x86_64/configuration/
Configuration file:
file:/home/simao/.eclipse/org.eclipse.platform_4.3.2_1543616141_linux_gtk_x86_64/configuration/config.ini loaded
Loading timestamp file from:
file:/home/simao/.eclipse/org.eclipse.platform_4.3.2_1543616141_linux_gtk_x86_64/configuration/ .baseConfigIniTimestamp
Timestamps found:
config.ini in the base: 1393237980000
remembered 1393237980000
Shared configuration location:
file:/usr/share/eclipse/configuration/
Framework located:
file:/usr/share/eclipse/plugins/org.eclipse.osgi_3.9.1.v20140110-1610.jar
Loading extension: reference:file:../../../../home/simao/.eclipse/org.eclipse.platform_4.3.2_1543616141_linux_gtk_x86_64/plugins/org.eclipse.equinox.weaving.hook_1.0.200.v20120524-1707.jar
eclipse.properties not found
Framework classpath:
file:/usr/share/eclipse/plugins/org.eclipse.osgi_3.9.1.v20140110-1610.jar
file:/usr/share/eclipse/plugins/
file:/usr/share/eclipse/plugins/../../../../home/simao/.eclipse/org.eclipse.platform_4.3.2_1543616141_linux_gtk_x86_64/plugins/org.eclipse.equinox.weaving.hook_1.0.200.v20120524-1707.jar
Splash location:
/usr/share/eclipse//plugins/org.eclipse.platform_4.3.2.v20140221-1700/splash.bmp
Debug options:
file:/home/simao/.options not found
Time to load bundles: 41
org.eclipse.m2e.logback.configuration: The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized. Will retry after the state location is initialized.
Starting application: 9429
!SESSION 2014-03-28 18:55:10.163 -----------------------------------------------
eclipse.buildId=4.3.2.M20140221-1700
java.version=1.7.0_51
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=pt_PT
Framework arguments: -product org.eclipse.epp.package.standard.product
Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.standard.product -clean -consoleLog -debug
!ENTRY org.eclipse.core.resources 2 10035 2014-03-28 18:55:21.761
!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.
org.eclipse.m2e.logback.configuration: Logback config file: /home/simao/Documents/Workspace/Educare/.metadata/.plugins/org.eclipse.m2e.logback.configuration/logback.1.4.0.20130601-0317.xml
org.eclipse.m2e.logback.configuration: Initializing logback
org.eclipse.m2e.logback.configuration: eclipse.consoleLog=true
No bp log location saved, using default.
[000:000] Cpu: 16.4.2, x4, 3010Mhz, 7989MB
[000:000] Computer model: Not available
No bp log location saved, using default.
[000:000] Cpu: 16.4.2, x4, 3010Mhz, 7989MB
[000:000] Computer model: Not available
[000:000] Browser XEmbed support present: 1
[000:000] Browser toolkit is Gtk2.
[000:000] Using Gtk2 toolkit
[000:036] Warning(optionsfile.cc:47): Load: Could not open file, err=2
[000:036] No bp log location saved, using default.
[000:036] Cpu: 16.4.2, x4, 3010Mhz, 7989MB
[000:037] Computer model: Not available
[000:037] Browser XEmbed support present: 1
[000:037] Browser toolkit is Gtk2.
[000:037] Using Gtk2 toolkit
[000:046] Warning(optionsfile.cc:47): Load: Could not open file, err=2
[000:046] No bp log location saved, using default.
[000:047] Cpu: 16.4.2, x4, 3010Mhz, 7989MB
[000:047] Computer model: Not available
[000:038] Warning(optionsfile.cc:47): Load: Could not open file, err=2
[000:038] No bp log location saved, using default.
[000:039] Cpu: 16.4.2, x4, 3010Mhz, 7989MB
[000:039] Computer model: Not available
[000:039] Browser XEmbed support present: 1
[000:039] Browser toolkit is Gtk2.
[000:039] Using Gtk2 toolkit
[000:048] Warning(optionsfile.cc:47): Load: Could not open file, err=2
[000:048] No bp log location saved, using default.
[000:049] Cpu: 16.4.2, x4, 3010Mhz, 7989MB
[000:049] Computer model: Not available
java version "1.7.0_51"
OpenJDK Runtime Environment (IcedTea 2.4.5) (ArchLinux build 7.u51_2.4.5-1-x86_64)
OpenJDK 64-Bit Server VM (build 24.51-b03, mixed mode)Can anyone help me debug this problem? I have no idea what to do next since the logs aren't outputing anything I can work with.
I've also tried to download a zip of eclipse from the official site and then run that eclipse executable but I got the same results.
Last edited by Lasering (2014-03-28 21:23:30)
Offline
When Eclipse crashes frequently, I often find that a recent webkitgtk update is to blame.
Try switching to the mozilla swt browser backend. It solved the problem for me.
To do that, add the following system property to the "-vmargs" argument within your /usr/share/eclipse/eclipse.ini:
-Dorg.eclipse.swt.browser.DefaultType=mozilla
Offline
Still crashes, but much less frequently. Thanks a lot, you are a life safer.
Offline