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

MethodArityHistogram should use Compile_lock in favour of fancy checks

    Details

    • Type: Enhancement
    • Status: Resolved
    • Priority: P4
    • Resolution: Fixed
    • Affects Version/s: 16
    • Fix Version/s: 16
    • Component/s: hotspot
    • Labels:
      None
    • Subcomponent:
    • Introduced In Version:
      12
    • Resolved In Build:
      master
    • CPU:
      generic
    • OS:
      generic

      Description

      Back in 2018, JDK-8209588, and shortly after, JDK-8209950 was filed. The remedy to the observed SIGSEGV was to call a method which would use heuristics, guided by prior observations, to find out if the storage at hand was safe to be interpreted a nmethod object.

      Meanwhile, further insights led to the conclusion that the Compile_lock should be held (in addition to the CodeCache_lock) while constructing the MethodArityHistogram. Holding that additional lock would make it obsolete to rely on heuristics.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                lucy Lucy Schmidt
                Reporter:
                lucy Lucy Schmidt
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: