Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-8777 XULRunner and Eclipse 3.7 issues
  3. JBIDE-9144

VPE crashes with Eclipse 3.7 on some Linux distributions

    XMLWordPrintable

Details

    Description

      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:

      1. Launch VpeAllTests from org.jboss.tools.vpe.ui.test plugin.
      2. New instance of Eclipse will be started.
      3. On the "Welcome Screen" click on "Workbench" arrow to enter workspace.
      4. Tests are about to execute.
      5. Eclipse crashes with the message:

        '#
        '# 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/
        '#

      6. Note: when the Welcome screen is active – JUnit tests go fine. Only after it is closed – fatal error is appeared.
      7. 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:

      1. Installed jbds-eap-5.0.0.m2-h657
      2. Created Seam war project
      3. Opened few pages in VPE
      4. Switched to another workspace, after that crash, Log attached

        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]

      Attachments

        1. hs_err_pid13234.log
          93 kB
        2. hs_err_pids.tar.gz
          638 kB
        3. org.eclipse.swt.gtk.linux.x86.zip
          3.62 MB
        4. org.eclipse.swt.gtk.x86_64.zip
          3.78 MB
        5. org.jboss.tools.xulrunner.initializer.patch
          1 kB
        6. org.jboss.tools.xulrunner.initializer.patch2
          1 kB
        7. WebKit.diff
          1 kB

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-15878 Visual Page Editor conflicts with mobile palette because of sqllite incompatibility

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-15886 CLONE - Visual Page Editor conflicts with mobile palette because of sqllite incompatibility

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-9188 add system property to allow explicit disabling of the visual page in VPE

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-9231 Create patched SWT plugins for Linux GTK x86 and x86_64

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-10185 Installing JBoss Tools 3.3 into Eclipse causes some problems for the Welcome screen

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              snjeza_jira Snjezana Peco (Inactive)
              dmaliarevich_jira Denis Maliarevich (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: