[jbosstools-issues] [JBoss JIRA] (JBIDE-16308) Cannot start JBT 4.2.0.Alpha1 on Fedora 19
Nick Boldt (JIRA)
issues at jboss.org
Mon Dec 16 12:30:32 EST 2013
[ https://issues.jboss.org/browse/JBIDE-16308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931890#comment-12931890 ]
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 at 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 at 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.
> Cannot start JBT 4.2.0.Alpha1 on Fedora 19
> ------------------------------------------
>
> Key: JBIDE-16308
> URL: https://issues.jboss.org/browse/JBIDE-16308
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.2.0.Alpha1
> Environment: JBT 4.2.Alpha1, L64, Fedora 19, 64-bit, Open JDK 1.7
> Reporter: Jiri Peterka
> Priority: Blocker
> Fix For: 4.2.0.Alpha1
>
> Attachments: hs_err_pid17371.log
>
>
> Installing JBT on Eclipse -4.4.M4- 4.4.M3 JEE package (linux_64), after JBT installation update site and restart I have:
> {code}
> !ENTRY org.eclipse.osgi 4 0 2013-12-16 15:35:03.535
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> at java.util.ArrayList.iterator(ArrayList.java:814)
> at org.apache.felix.resolver.ResolverImpl.mergeUses(ResolverImpl.java:962)
> at org.apache.felix.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:787)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:252)
> at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolve(ModuleResolver.java:652)
> at org.eclipse.osgi.container.ModuleResolver.resolveDelta(ModuleResolver.java:75)
> at org.eclipse.osgi.container.ModuleContainer.resolveAndApply(ModuleContainer.java:454)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:412)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:402)
> at org.eclipse.osgi.container.Module.start(Module.java:406)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1530)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1510)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1481)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1424)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
> {code}
> Even if I raise a memory for JVM, Eclipse doesn't start but not error message is written
--
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
More information about the jbosstools-issues
mailing list