Details

    • Type: Enhancement
    • Status: Resolved
    • Priority: P4
    • Resolution: Fixed
    • Affects Version/s: 11
    • Fix Version/s: 11
    • Component/s: hotspot
    • Labels:
    • Subcomponent:
    • Resolved In Build:
      b10
    • CPU:
      generic
    • OS:
      generic

      Description

      There are occasions when some insight into the current state of the JVM code heap would be helpful to answer questions like
       * Why is the JIT turned off and then on again and again?
       * Where has all the code heap space gone?
       * Why is the method sweeper not working effectively?

      Implement an on-the-fly analysis of the code heap. Trigger analysis and output via command-line parameter (state when vm shuts down) and via jcmd (at any time).

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: