Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8220643

[AOT] NullPointerException in org.graalvm.compiler.options.OptionKey$Lazy.<clinit>

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: P2 P2
    • 13
    • 13
    • hotspot
    • 13

      A lot of jck tests started to fail with

      java.lang.ExceptionInInitializerError
      at jdk.internal.vm.compiler@13-internal/org.graalvm.compiler.options.OptionKey.checkDescriptorExists(OptionKey.java:64)
      at jdk.internal.vm.compiler@13-internal/org.graalvm.compiler.options.OptionKey.getValue(OptionKey.java:139)
      at jdk.internal.vm.compiler@13-internal/org.graalvm.compiler.hotspot.HotSpotGraalCompilerFactory.initializeGraalCompilePolicyFields(HotSpotGraalCompilerFactory.java:91)
      at jdk.internal.vm.compiler@13-internal/org.graalvm.compiler.hotspot.HotSpotGraalCompilerFactory.onSelection(HotSpotGraalCompilerFactory.java:76)
      at jdk.internal.vm.ci/jdk.vm.ci.hotspot.HotSpotJVMCICompilerConfig.getCompilerFactory(HotSpotJVMCICompilerConfig.java:106)
      at jdk.internal.vm.ci/jdk.vm.ci.hotspot.HotSpotJVMCIRuntime.<init>(HotSpotJVMCIRuntime.java:296)
      at jdk.internal.vm.ci/jdk.vm.ci.hotspot.HotSpotJVMCIRuntime$DelayedInit.<clinit>(HotSpotJVMCIRuntime.java:79)
      at jdk.internal.vm.ci/jdk.vm.ci.hotspot.HotSpotJVMCIRuntime.runtime(HotSpotJVMCIRuntime.java:95)
      at jdk.internal.vm.ci/jdk.vm.ci.runtime.JVMCI.initializeRuntime(Native Method)
      at jdk.internal.vm.ci/jdk.vm.ci.runtime.JVMCI.<clinit>(JVMCI.java:58)
      Caused by: java.lang.NullPointerException
      at jdk.internal.vm.compiler@13-internal/org.graalvm.compiler.options.OptionKey$Lazy.<clinit>(OptionKey.java:91)

      when running with with AOTed jdk.internal.vm.compiler in Graal as JIT mode.

      This issues started to occur after JDK-8218074 "Update Graal" was integrated.

            iveresov Igor Veresov
            epavlova Ekaterina Pavlova
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: