Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Blocker
    • Resolution: Done
    • Affects Version/s: 4.2.0.Alpha1
    • Fix Version/s: 4.2.0.Alpha2
    • Component/s: xulrunner
    • Labels:
      None
    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      1. Use Eclipse 4.4.0.M4 instead of M3
      2. Use `export SWT_GTK3=0` before running Eclipse
      3. Disable VPE from using Xulrunner using `-Dorg.jboss.tools.vpe.loadxulrunner=false` in your eclipse.ini's vmargs.

      Show
      1. Use Eclipse 4.4.0.M4 instead of M3 2. Use `export SWT_GTK3=0` before running Eclipse 3. Disable VPE from using Xulrunner using `-Dorg.jboss.tools.vpe.loadxulrunner=false` in your eclipse.ini's vmargs.

      Description

      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:

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

      I'm running on Ubuntu 12.04.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  snjeza Snjezana Peco
                  Reporter:
                  mickael_istria Mickael Istria
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  12 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: