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

NMethod state machine is not monotonic

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: P3
    • Resolution: Fixed
    • Affects Version/s: 13
    • Fix Version/s: 13
    • Component/s: hotspot
    • Subcomponent:
    • Resolved In Build:
      b31

      Backports

        Description

        When two concurrent threads request different nmethod state transitions with different levels of dead, it sometimes happens that monotonicity of the state transitions is lost, and as a result, nmethods may resurrect in unfortunate races, and cause the VM to crash.

        Today, it is up to the caller to know if there could be any racing transitions, but it is very easy to slip. I can see a few examples of such slippage.

        However, the state transitions really should be monotonic; an nmethod is always be at least as dead as the most dead state requested.

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                eosterlund Erik Österlund
                Reporter:
                eosterlund Erik Österlund
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved: