[ https://issues.jboss.org/browse/JBIDE-16308?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-16308 at 12/16/13 12:29 PM: --------------------------------------------------------------- I can reproduce this on Fedora 18 using this launch script for Eclipse 4.4.M3 Standard (not JEE) bundle, installing ALL categorized features from http://download.jboss.org/jbosstools/updates/JBossTools-4.2.0.Alpha1.core/. {code} $➔ uname -a Linux thunk 3.11.9-100.fc18.x86_64 #1 SMP Wed Nov 20 21:22:39 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux $➔ /opt/sun-java2-7.0/bin/java -version java version "1.7.0_17" Java(TM) SE Runtime Environment (build 1.7.0_17-b02) Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode) {code} {code} #!/bin/bash workspace=/home/nboldt/eclipse/workspace-clean44 target=/home/nboldt/eclipse/44clean eclipse=/home/nboldt/tmp/Eclipse_Bundles/eclipse-standard-luna-M3-linux-gtk-x86_64.tar.gz cd ${target} if [[ $1 == "e" ]]; then echo "Wipe $target/eclipse and $workspace ..." rm -fr $target/eclipse $workspace echo "Unpack $eclipse ..." tar xzf $eclipse shift fi #export GDK_NATIVE_WINDOWS=true ${target}/eclipse/eclipse -clean -showLocation -data $workspace -consolelog -console -vm /opt/sun-java2-7.0/bin/java "$*" 2>&1 | tee "logs/eclipse.log.`date`.txt" {code} After installation and cold restart w/ -debug flag, I get this crash, though it took 6 minutes to appear: {code} [11:47:38] nboldt@thunk:~/eclipse/44clean $➔ ./e -debug Install location: file:/home/nboldt/eclipse/44clean/eclipse/ Configuration file: file:/home/nboldt/eclipse/44clean/eclipse/configuration/config.ini loaded Configuration location: file:/home/nboldt/eclipse/44clean/eclipse/configuration/ Framework located: file:/home/nboldt/eclipse/44clean/eclipse/plugins/org.eclipse.osgi_3.10.0.v20131024-2025.jar Loading extension: reference:file:org.eclipse.osgi.compatibility.state_1.0.0.v20131023-1243.jar eclipse.properties not found Loading extension: reference:file:org.eclipse.birt.jetty.overlay_4.3.1.v201308301349.jar eclipse.properties not found Framework classpath: file:/home/nboldt/eclipse/44clean/eclipse/plugins/org.eclipse.osgi_3.10.0.v20131024-2025.jar file:/home/nboldt/eclipse/44clean/eclipse/plugins/ file:/home/nboldt/eclipse/44clean/eclipse/plugins/org.eclipse.osgi.compatibility.state_1.0.0.v20131023-1243.jar file:/home/nboldt/eclipse/44clean/eclipse/plugins/org.eclipse.birt.jetty.overlay_4.3.1.v201308301349.jar Splash location: /home/nboldt/eclipse/44clean/eclipse//plugins/org.eclipse.platform_4.4.0.v20131030-2000/splash.bmp Debug options: file:/home/nboldt/eclipse/44clean/.options not found Time to load bundles: 45 Starting application: 338649 osgi> # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007f8429af2255, pid=18745, tid=140208137373440 # # JRE version: 7.0_17-b02 # Java VM: Java HotSpot(TM) 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libxul.so+0xc81255] JSD_DebuggerOnForUser+0x978a2 # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # An error report file with more information is saved as: # /home/nboldt/eclipse/44clean/hs_err_pid18745.log # # If you would like to submit a bug report, please visit: # http://bugreport.sun.com/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # Start VM: /opt/sun-java2-7.0/bin/java -Dosgi.requiredJavaVersion=1.6 -XX:MaxPermSize=256m -Xms40m -Xmx512m -jar /home/nboldt/eclipse/44clean/eclipse//plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar -os linux -ws gtk -arch x86_64 -showsplash /home/nboldt/eclipse/44clean/eclipse//plugins/org.eclipse.platform_4.4.0.v20131030-2000/splash.bmp -launcher /home/nboldt/eclipse/44clean/eclipse/eclipse -name Eclipse --launcher.library /home/nboldt/eclipse/44clean/eclipse//plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.200.v20131025-1931/eclipse_1601.so -startup /home/nboldt/eclipse/44clean/eclipse//plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar --launcher.appendVmargs -exitdata cb802d -product org.eclipse.epp.package.standard.product -clean -showLocation -data /home/nboldt/eclipse/workspace-clean44 -consolelog -console -debug -vm /opt/sun-java2-7.0/bin/java -vmargs -Dosgi.requiredJavaVersion=1.6 -XX:MaxPermSize=256m -Xms40m -Xmx512m -jar /home/nboldt/eclipse/44clean/eclipse//plugins/org.eclipse.equinox.launcher_1.3.0.v20130327-1440.jar [11:53:39] nboldt@thunk:~/eclipse/44clean {code} was (Author: nickboldt): I can reproduce this on Fedora 18 using this launch script for Eclipse 4.4.M3 Standard (not JEE) bundle, installing ALL categorized features from http://download.jboss.org/jbosstools/updates/JBossTools-4.2.0.Alpha1.core/. {code} $➔ uname -a Linux thunk 3.11.9-100.fc18.x86_64 #1 SMP Wed Nov 20 21:22:39 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux $➔ /opt/sun-java2-7.0/bin/java -version java version "1.7.0_17" Java(TM) SE Runtime Environment (build 1.7.0_17-b02) Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode) {code} {code} #!/bin/bash workspace=/home/nboldt/eclipse/workspace-clean44 target=/home/nboldt/eclipse/44clean eclipse=/home/nboldt/tmp/Eclipse_Bundles/eclipse-standard-luna-M3-linux-gtk-x86_64.tar.gz cd ${target} if [[ $1 == "e" ]]; then echo "Wipe $target/eclipse and $workspace ..." rm -fr $target/eclipse $workspace echo "Unpack $eclipse ..." tar xzf $eclipse shift fi #export GDK_NATIVE_WINDOWS=true ${target}/eclipse/eclipse -clean -showLocation -data $workspace -consolelog -console -vm /opt/sun-java2-7.0/bin/java "$*" 2>&1 | tee "logs/eclipse.log.`date`.txt" {code} After installation and warm restart, I get this: {code} Wipe /home/nboldt/eclipse/44clean/eclipse and /home/nboldt/eclipse/workspace-clean44 ... Unpack /home/nboldt/tmp/Eclipse_Bundles/eclipse-standard-luna-M3-linux-gtk-x86_64.tar.gz ... osgi> osgi> # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007f7e952f2255, pid=15646, tid=140184237340416 # # JRE version: 7.0_17-b02 # Java VM: Java HotSpot(TM) 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libxul.so+0xc81255] JSD_DebuggerOnForUser+0x978a2 # # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # An error report file with more information is saved as: # /home/nboldt/eclipse/43clean/hs_err_pid15646.log # # If you would like to submit a bug report, please visit: # http://bugreport.sun.com/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # {code} Same crash occurs for a cold restart, though it may take over a minute for the crash to occur. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira