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

NativeMemoryTracking is handled by launcher inconsistenly

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: P4
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 17
    • Component/s: tools
    • Labels:
      None
    • Subcomponent:
    • Resolved In Build:
      b07
    • CPU:
      generic
    • OS:
      generic

      Description

      There is inconsistency how launcher and hotspot handle -XX:NativeMemoryTracking for non-java(w)

      For all launcher-based tools launcher ignores the parameter but hotspot handles it.
      As a result VM warning is printed:
      > jcmd -J-XX:NativeMemoryTracking=detail
      Java HotSpot(TM) 64-Bit Server VM warning: Native Memory Tracking did not setup properly, using wrong launcher?
      20508 jdk.jcmd/sun.tools.jcmd.JCmd

      > jar -J-XX:NativeMemoryTracking=detail
      Java HotSpot(TM) 64-Bit Server VM warning: Native Memory Tracking did not setup properly, using wrong launcher?
      Usage: jar [OPTION...] [ [--release VERSION] [-C dir] files] ...
      Try `jar --help' for more information.

      As far as I see from history, this was implemented this way initially (JDK-8042469), CCC request tells nothing about java/non-java launcher differences.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              amenkov Alex Menkov
              Reporter:
              amenkov Alex Menkov
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: