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

Move StackWatermark handling out of LockStack::contains

    XMLWordPrintable

Details

    • b25

    Backports

      Description

        There are StackWatermark handling inside LockStack::contains. This is an indication that either, some thread has failed to start its own StackWatermark processing, or that some thread is looking into the oops of another thread without starting the StackWatermark handling. The later is usually more common.

        I propose that we hoist the StackWatermark processing out of the LockStack into the code that actually performs these reads of the oops.

        Attachments

          Issue Links

            Activity

              People

                stefank Stefan Karlsson
                stefank Stefan Karlsson
                Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: