[jbosstools-issues] [JBoss JIRA] (JBIDE-19750) Install grinder fails to run on RHEL7: No more handles!

[Konstantin Marmalyukov (JIRA)]

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

Konstantin Marmalyukov commented on JBIDE-19750:
------------------------------------------------

[~fbricon] this is not a good idea. Reasons:
1. There is no 64bit webkit for Windows
2. 32bit Webkit on Windows requres Safari to be installed.
3. When JSF mode in VPE will be turned on, there is a good chance for Eclipse to be crashed because of webkit and xulrunner conflict(if Webkit is installed and you use GTK2)

I'd rather use the same approach we use for Visual Editor for HTML files or in preview in [HTML5 wizards in Palette|https://github.com/jbosstools/jbosstools-jst/blob/master/plugins/org.jboss.tools.jst.web.ui/src/org/jboss/tools/jst/web/ui/WebUiPlugin.java#L158]. We use default browser everywhere(SWT.NONE). On Mac it is Webkit, on Windows it is IE. On Linux GTK3 it is Webkit(using Webkit as a default browser for GTK3 is forced by VPE). On Linux GTK2 we add a dialog for VPE to choose between Webkit and XulRunner.

The problem that you may have is when XulRunner is turned on on Linux GTK2. Your Central implementation looks beautiful, so I guess a lot of HTML5 features was used there, which unfortunately is not supported by XulRunner. Anyway, we should take a look how ugly Central will look with our XulRunner at first.

> Install grinder fails to run on RHEL7: No more handles!
> -------------------------------------------------------
>
>                 Key: JBIDE-19750
>                 URL: https://issues.jboss.org/browse/JBIDE-19750
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 4.3.0.Beta1
>            Reporter: Nick Boldt
>            Assignee: Mickael Istria
>
> {code}
> 16:48:30 Installing org.eclipse.swtbot.eclipse.test.junit.feature.group 2.2.1.201402241301.
> ...
> 13:39:08 !MESSAGE Internal browser is not available: No more handles [Browser style SWT.MOZILLA and Java system property org.eclipse.swt.browser.DefaultType=mozilla are not supported with GTK 3 as XULRunner is not ported for GTK 3 yet]
> 13:43:18 Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 253.079 sec
> 13:43:18 
> 13:43:18 Testcase: testInstall took 252.166 sec
> {code} - https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_9.0.mars/job/jbosstools-install-grinder.install-tests.matrix_master/2801/PROJECT=devstudio,eclipseBundleVersion=mars.M6,jdk=java18_default,label_exp=%28RHEL7||beaker||jboss-prod%29&&!ia64&&!ppc64&&!rhts/console
> I tried to run using `-Dorg.eclipse.swt.browser.DefaultType=webkit` as a script param for  `testInstall.groovy` but it must not have passed through to the eclipse install process, as the above error suggests.
> Wondering if ...
> a) passing through a different *swt.browser.DefaultType*, &/or 
> b) using a newer SWTBot (which works with Luna [1] now?)
> ... might help.
> [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=464619



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)