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

Crash holding 'access' lock can deadlock in JVMCI compiler thread

    Details

    • Type: Bug
    • Status: Open
    • Priority: P4
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: tbd
    • Component/s: hotspot
    • Labels:
    • Subcomponent:
      gc
    • CPU:
      generic
    • OS:
      generic

      Description

      If we have a crash (segfault &etc) while holding one of G1's 'access' rank locks in a JVMCI compiler thread, we can deadlock (or recursively crash in a debug build). The problem is that printing the stack trace for such a thread typically prints an nmethod, which for JVMCI involves resolving a jweak. If that jweak resolve itself hits a case in the SATB barrier where the same 'access' lock is needed, we deadlock in a product build, or crash in the crash handler in a debug build. (Fortunately, the crash handler is pretty robust against such recursive failures.)

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                kbarrett Kim Barrett
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated: