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

possible deadlock due to locking java.lang.Class monitors

XMLWordPrintable

    • jit
    • 1.1.1
    • generic
    • generic
    • Not verified

      There are two monitors for each class. The monitor associated with the
      handle of a java.lang.Class object should only be used for synchronized
      methods and other Java-level synchronization. The monitor associated
      with the ClassClass structure should be used for all internal locking in
      the VM and JIT compiler.

      The JIT support code for the first call to a native method is currently
      using the wrong monitor. It needs to use the one associated with the
      ClassClass structure. The current code may deadlock. The problem exists
      in both the SPARC and i386 versions.

            duke J. Duke
            duke J. Duke
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: