[jbosstools-issues] [JBoss JIRA] (JBIDE-16280) VPE/XulRunner crashes workbench

[Snjezana Peco (JIRA)]

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

Snjezana Peco commented on JBIDE-16280:
---------------------------------------

{quote}
So the solution is "just" to rebuild xulrunner against GTK3 ?
{quote}

If we want to start XULRunner with SWT GTK3, it has to be linked to GTK3.
Since that isn't trivial (neither firefox nor chrome has been ported to GTK3 yet), we could do the following:
- if Eclipse is started with GTK3, we would have to disable XULRunner. Eclipse won't freeze in this case.
- if a user tries to open the VPE editor, we would warn him to start Eclipse with GTK2 in order to use VPE

                
> VPE/XulRunner crashes workbench
> -------------------------------
>
>                 Key: JBIDE-16280
>                 URL: https://issues.jboss.org/browse/JBIDE-16280
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: xulrunner
>    Affects Versions: 4.2.0.Alpha1
>            Reporter: Mickael Istria
>            Priority: Critical
>         Attachments: hs_err_pid20688.log
>
>
> After an install of JBDS 8.0.0.Alpha1 from installer (built locally with fixes from JBDS-2861), the application crashes a few seconds after startup.
> JVM creates me a thread dump, that you can find attached. Here is the header:
> {code}
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGSEGV (0xb) at pc=0x00007fdea49f3255, pid=18578, tid=140596949411584
> #
> # JRE version: 7.0_25-b30
> # Java VM: OpenJDK 64-Bit Server VM (23.7-b01 mixed mode linux-amd64 compressed oops)
> # Problematic frame:
> # C  [libxul.so+0xc81255]  JSD_DebuggerOnForUser+0x978a2
> #
> {code}
> I'm running on Ubuntu 12.04.

--
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