1:06 p.m.
[
https://issues.jboss.org/browse/JBIDE-16308?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-16308:
------------------------------------
Installing from http://download.jboss.org/jbosstools/updates/nightly/core/4.2.luna/ into
Eclipse Standard 4.4.M3 and selecting only *org.jboss.tools.community.central.feature*
results in the same crash...
{code}
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007fb157572255, pid=21996, tid=140400201221888
#
# 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
{code}
Here's the debug output showing the eclipse.ini / commandline settings:
{code}
-debug
-vm /opt/sun-java2-7.0/bin/java
-vmargs
-Dosgi.requiredJavaVersion=1.6
-XX:MaxPermSize=256m
-Xms40m
-Xmx512m
{code}
but based on a smaller set of installed features:
{code}
$➔ find . -maxdepth 1 -name "*jboss*" -o -name "*hibernate*" | sort
./org.hibernate.eclipse.feature_3.8.0.Alpha1-v20131207-1621-B2
./org.jboss.ide.eclipse.archives.feature_3.5.0.Alpha1-v20131209-0714-B4
./org.jboss.ide.eclipse.as.archives.integration.feature_2.5.0.Alpha1-v20131209-0714-B4
./org.jboss.ide.eclipse.as.feature_2.5.0.Alpha1-v20131209-0714-B4
./org.jboss.ide.eclipse.as.jmx.integration.feature_2.5.0.Alpha1-v20131209-0714-B4
./org.jboss.ide.eclipse.as.serverAdapter.wtp.feature_2.5.0.Alpha1-v20131209-0714-B4
./org.jboss.ide.eclipse.as.server.rse.integration.feature_2.5.0.Alpha1-v20131209-0714-B4
./org.jboss.tools.archives.scanner.feature_3.5.0.Alpha1-v20131209-0714-B4
./org.jboss.tools.central.feature_1.3.0.Alpha1-v20131209-0943-B6
./org.jboss.tools.common.feature_3.6.0.Alpha1-v20131206-2157-B1
./org.jboss.tools.community.central.feature_1.3.0.Alpha1-v20131209-0943-B6
./org.jboss.tools.community.project.examples.feature_1.6.0.Alpha1-v20131209-0943-B6
./org.jboss.tools.jmx.feature_1.5.0.Alpha1-v20131209-0714-B4
./org.jboss.tools.jsf.feature_3.6.0.Alpha1-v20131209-0801-B5
./org.jboss.tools.jst.feature_3.6.0.Alpha1-v20131207-1423-B2
./org.jboss.tools.maven.project.examples.feature_1.6.0.Alpha1-v20131209-0943-B6
./org.jboss.tools.project.examples.feature_1.6.0.Alpha1-v20131209-0943-B6
./org.jboss.tools.runtime.core.feature_3.0.0.Alpha1-v20131206-2157-B1
./org.jboss.tools.runtime.seam.detector.feature_3.5.0.Alpha1-v20131209-0801-B5
./org.jboss.tools.seam.feature_3.5.0.Alpha1-v20131209-0801-B5
./org.jboss.tools.stacks.core.feature_1.1.0.Alpha1-v20131206-2157-B1
./org.jboss.tools.vpe.feature_3.5.100.Alpha1-v20131210-2123-B4
{code}
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, hs_err_pid18745.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
4502
days inactive
4502
days old
jbosstools-issues@lists.jboss.org
0 comments
1 participants
participants (1)
-
Nick Boldt (JIRA)