[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-9144) VPE crashes with Eclipse 3.7 on some Linux distributions

Snjezana Peco (JIRA) jira-events at lists.jboss.org
Tue Jun 21 14:55:24 EDT 2011


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

Snjezana Peco commented on JBIDE-9144:
--------------------------------------

> Snjezana, please apply your
> org.jboss.tools.xulrunner.initializer.patch in brunch/trunk. At least, it does not make the things worse if used with a non-patched SWT.

I have committed the changed patch so that now the user can enable WebKit.
If the user doesn't add any property, XULRunner will be loaded and WebKit disabled (if the patched swt plugins are included).
The user can disable XULRunner and enable WebKit by adding the following properties:
-Dorg.jboss.tools.vpe.loadxulrunner=false -Dorg.eclipse.swt.browser.UseWebKitGTK=true

The org.eclipse.swt.browser.UseWebKitGTK property is available on Linux GTK only.

I have also configured o.j.t.xulrunner.initializer as a singleton.

> VPE crashes with Eclipse 3.7 on some Linux distributions
> --------------------------------------------------------
>
>                 Key: JBIDE-9144
>                 URL: https://issues.jboss.org/browse/JBIDE-9144
>             Project: Tools (JBoss Tools)
>          Issue Type: Sub-task
>          Components: Visual Page Editor core
>    Affects Versions: 3.3.0.M2
>            Reporter: Denis Maliarevich
>            Assignee: Snjezana Peco
>            Priority: Critical
>             Fix For: 3.3.0.M2
>
>         Attachments: hs_err_pid13234.log, hs_err_pids.tar.gz, org.eclipse.swt.gtk.linux.x86.zip, org.eclipse.swt.gtk.x86_64.zip, org.jboss.tools.xulrunner.initializer.patch, org.jboss.tools.xulrunner.initializer.patch2, WebKit.diff
>
>
> VPE crashes with Eclipse 3.7 on some Linux distributions:
> ||OS||XULRunner version||Crashes when unit-testing?||Crashes when using?||
> |Ubuntu 10 x86|1.9.1, 1.9.2.16, 1.9.2.17|*YES*|no|
> |Ubuntu 10 x86_64|1.9.2.16|no|no|
> |Ubuntu 10 x86_64|1.9.1|???|YES (no problem while we use 1.9.2)|
> |Fedora 14 x86|1.9.2.16|*YES*|no|
> |Fedora 15 x86_64|1.9.2.16|???|*YES*|
> |Gentoo x86|1.9.2.16|???|no|
> *Steps to reproduce JUnit crash:*
> # Launch VpeAllTests from org.jboss.tools.vpe.ui.test plugin.
> # New instance of Eclipse will be started.
> # On the "Welcome Screen" click on "Workbench" arrow to enter workspace.
> # Tests are about to execute.
> # Eclipse crashes with the message:
> {quote}
> '#
> '# A fatal error has been detected by the Java Runtime Environment:
> '#
> '#  SIGSEGV (0xb) at pc=0x7f11d0c1, pid=3688, tid=2218912624
> '#
> '# JRE version: 6.0_20-b20
> '# Java VM: OpenJDK Server VM (19.0-b09 mixed mode linux-x86 )
> '# Derivative: IcedTea6 1.9.7
> '# Distribution: Ubuntu 10.04.1 LTS, package 6b20-1.9.7-0ubuntu1~10.04.1
> '# Problematic frame:
> '# C  [libsqlite3.so+0x60c1]
> '#
> '# An error report file with more information is saved as:
> '# /home/ubuntu/projects/trunk/vpe/tests/org.jboss.tools.vpe.ui.test/hs_err_pid3688.log
> '#
> '# If you would like to submit a bug report, please include
> '# instructions how to reproduce the bug and visit:
> '#   https://bugs.launchpad.net/ubuntu/+source/openjdk-6/
> '#
> {quote}
> # Note: when the Welcome screen is active -- JUnit tests go fine. Only after it is closed -- fatal error is appeared.
> # Workaround: On "Run Configurations" > "Tracing" > Select plugin "org.eclipse.ui.intro" > Select "flags/noBrowser" checkbox. After that Welcome Screen will be different, tests won't fail.
> *Steps to reproduce the crash manually:*
> # Installed jbds-eap-5.0.0.m2-h657
> # Created Seam war project
> # Opened few pages in VPE
> # Switched to another workspace, after that crash, Log attached
> {quote}
> A fatal error has been detected by the Java Runtime Environment:
> SIGSEGV (0xb) at pc=0x00007fa5c8b86dd0, pid=13234, tid=140351893849856
> Problematic frame:
> C [libsqlite3.so+0x10dd0]
> {quote}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the jbosstools-issues mailing list