[jbosstools-issues] [JBoss JIRA] (JBIDE-16308) Cannot start JBT 4.2.0.Alpha1 on Fedora 19

[Mickael Istria (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-16308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932007#comment-12932007 ] 

Mickael Istria commented on JBIDE-16308:
----------------------------------------

That's something to discuss with [~maxandersen], but I don't think we can't tell users to set SWT_GTK3 setting in their Eclipse IDE when they install JBoss Tools.
GTK3 is the biggest part of migration to Luna, and Alpha1 is meant to provide minimal compatibility with Luna (and then GTK3). So let's say that Alpha1 is not ready until XulRunner gets recompiled against GTK3.
                
> 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, xulrunner
>    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