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

Unloaded signature classes in DirectMethodHandles

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Fixed
    • Icon: P4 P4
    • 23
    • 23
    • core-libs
    • None

      JVM installs loader constraints for unloaded signature classes when method resolution occurs. MethodHandle resolution took a different route and eagerly resolves signature classes instead (see sun.invoke.util.VerifyAccess::isTypeVisible). There's a micro-optimization which bypasses that logic for java.* classes. The downside is that java.* classes can show up as unloaded signature classes. It manifests as inlining failures during JIT-compilation and may cause severe performance issues.

            vlivanov Vladimir Ivanov
            vlivanov Vladimir Ivanov
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: