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

[Denis Golovin (JIRA)]

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

Denis Golovin edited comment on JBIDE-16280 at 12/18/13 7:47 PM:
-----------------------------------------------------------------

FAQ should be updated then in wiki and mention this problem. It is probably good idea to mention this workaround right in VPE part error message when xulrunner plugin is found but SWT_GTK3 is not exported.
                
      was (Author: dgolovin):
    FAQ should be updated then in wiki and mention this problem. It probably good idea to mention this workaround right in VPE part error message.
                  
> 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
>             Fix For: 4.2.0.Alpha2
>
>         Attachments: hs_err_pid20688.log, install-locally-built-vpe-from-4-sites.png
>
>
> 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