REDO: Force clients to explicitly pass mem_tag value, even if it is mtNone

XMLWordPrintable

    • Type: Enhancement
    • Resolution: Fixed
    • Priority: P4
    • 25
    • Affects Version/s: None
    • Component/s: hotspot
    • b21

      This is a followup to JDK-8328944, which addressed some cases where mtNone showed up in reports, but there is more to do here.

      Here we mainly concentrate on removing the default parameter, so that no-one is tempted to use the APIs without providing the mem tag, if known.

            Assignee:
            Gerard Ziemski (Inactive)
            Reporter:
            Gerard Ziemski (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: