Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-28656

Eclipse (with JBoss Tools, Java 17) crashes when creating Node.js component from Devfile Registry when Dev Sandbox does not show any project

    XMLWordPrintable

Details

    • Bug
    • Resolution: Cannot Reproduce
    • Major
    • 4.26.0.AM1
    • 4.25.0.AM1
    • openshift
    • None
    • Sprint #226 Oct 2022
    • Hide

      1. Connect in OS app. Explorer to the Dev Sandbox
      Update: after eclipse restart, sometime it happens that dev folder in sandbox is not shown, and crash happens during this setup
      2. Create an empty project in the workspace
      3. List DevFile registry for nodejs project and create new component.
      4. In the wizard, choose empty project and use nodejs starter project to create an app.
      5. Assert: Component and project is created.
      Actual result: Nothing happens, eclipse freezes and crashes in a while.

      Show
      1. Connect in OS app. Explorer to the Dev Sandbox Update: after eclipse restart, sometime it happens that dev folder in sandbox is not shown, and crash happens during this setup 2. Create an empty project in the workspace 3. List DevFile registry for nodejs project and create new component. 4. In the wizard, choose empty project and use nodejs starter project to create an app. 5. Assert: Component and project is created. Actual result: Nothing happens, eclipse freezes and crashes in a while.
    • ---

    Description

      Eclipse crashes on fatal error in JVM with SIGSEGV signal.

      I am connected to DevSandbox and I am creating a Node.js component with node js started app from the devfile registry.

      $ ./eclipse 
      WARNING: Using incubator modules: jdk.incubator.vector, jdk.incubator.foreign
      [3090655:3090670:0926/142857.076608:ERROR:ssl_client_socket_impl.cc(983)] handshake failed; returned -1, SSL error code 1, net_error -202
      org.eclipse.m2e.logback.configuration: Activated before the state location was initialized. Retry after the state location is initialized.
      [3090655:3090670:0926/142927.040069:ERROR:ssl_client_socket_impl.cc(983)] handshake failed; returned -1, SSL error code 1, net_error -202
      [3090655:3090670:0926/142927.041108:ERROR:ssl_client_socket_impl.cc(983)] handshake failed; returned -1, SSL error code 1, net_error -202
      org.eclipse.m2e.logback.configuration: Logback config file: /home/odockal/eclipse-workspace-JBT4250AM1/.metadata/.plugins/org.eclipse.m2e.logback.configuration/logback.2.0.0.20220705-1221.xml
      org.eclipse.m2e.logback.configuration: Initializing logback
      Error in cpuinfo: failed to parse processor information from /proc/cpuinfo
      Sep 26, 2022 2:29:52 PM org.eclipse.lsp4mp.ls.MicroProfileLanguageServer initialize
      INFO: Initializing MicroProfile server 0.4.0-20220324-1654 with /usr/lib/jvm/java-17-openjdk-17.0.4.1.1-1.fc36.x86_64
      Sep 26, 2022 2:29:52 PM com.redhat.qute.ls.QuteLanguageServer initialize
      INFO: Initializing Qute server 0.11.1-20220325-1628 with /usr/lib/jvm/java-17-openjdk-17.0.4.1.1-1.fc36.x86_64
      log4j:WARN No appenders could be found for logger (org.apache.http.client.protocol.RequestAddCookies).
      log4j:WARN Please initialize the log4j system properly.
      log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
      Sep 26, 2022 2:29:57 PM org.eclipse.lsp4mp.jdt.internal.core.AbstractMicroProfileProviderRegistry loadExtensionProviders
      INFO: ->- Loading .configSourceProviders extension point ->-
      Sep 26, 2022 2:29:57 PM org.eclipse.lsp4mp.jdt.internal.core.AbstractMicroProfileProviderRegistry addExtensionProviders
      INFO:   Loaded configSourceProviders: com.redhat.microprofile.jdt.internal.quarkus.providers.QuarkusConfigSourceProvider
      Sep 26, 2022 2:29:57 PM org.eclipse.lsp4mp.jdt.internal.core.AbstractMicroProfileProviderRegistry addExtensionProviders
      INFO:   Loaded configSourceProviders: org.eclipse.lsp4mp.jdt.internal.core.providers.MicroProfileConfigSourceProvider
      Sep 26, 2022 2:29:57 PM org.eclipse.lsp4mp.jdt.internal.core.AbstractMicroProfileProviderRegistry loadExtensionProviders
      INFO: -<- Done loading .configSourceProviders extension point -<-
      Loop over:  window=org.eclipse.ui.internal.WorkbenchWindow@78333d5a
      #
      # A fatal error has been detected by the Java Runtime Environment:
      #
      #  SIGSEGV (0xb) at pc=0x00007fb702eca714, pid=3095758, tid=3099021
      #
      # JRE version: OpenJDK Runtime Environment (Red_Hat-17.0.4.1.1-1.fc36) (17.0.4.1+1) (build 17.0.4.1+1)
      # Java VM: OpenJDK 64-Bit Server VM (Red_Hat-17.0.4.1.1-1.fc36) (17.0.4.1+1, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
      # Problematic frame:
      # V  [libjvm.so+0x28a714]  AccessInternal::PostRuntimeDispatch<G1BarrierSet::AccessBarrier<548964ul, G1BarrierSet>, (AccessInternal::BarrierType)2, 548964ul>::oop_access_barrier(void*)+0x4
      #
      # Core dump will be written. Default location: Core dumps may be processed with "/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h" (or dumping to /home/odockal/Apps/eclipse/eclipse-jee-2022-09-RC1-JBT4250AM1/eclipse/core.3095758)
      #
      # An error report file with more information is saved as:
      # /home/odockal/Apps/eclipse/eclipse-jee-2022-09-RC1-JBT4250AM1/eclipse/hs_err_pid3095758.log
      #
      # If you would like to submit a bug report, please visit:
      #   https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=java-17-openjdk&version=36
      #
      
      

      Attachments

        Activity

          People

            jmaury@redhat.com Jeff MAURY
            odockal@redhat.com Ondrej Dockal
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: