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

ForceSafepoint operations should be more specific

    XMLWordPrintable

    Details

    • Type: Enhancement
    • Status: Resolved
    • Priority: P4
    • Resolution: Fixed
    • Affects Version/s: 9
    • Fix Version/s: 10
    • Component/s: hotspot
    • Labels:
      None
    • Subcomponent:
    • Resolved In Build:
      b21

      Description

      When investigating safepointing on a large application I found that out of 802 safepoints were "ForceSafepoint" operations.

      Looking at the sources, there are four completely unrelated situations (compilation, code sweeping, jvmti, class loading) which trigger this safepoint.

      It would be really nice if these situations could be distinguished somehow using logging.

      The affected areas are compiler and runtime, randomly assigning this issue to runtime for now. Feel free to reassign/create one for the compiler team.

        Attachments

          Activity

            People

            Assignee:
            rehn Robbin Ehn
            Reporter:
            tschatzl Thomas Schatzl
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: