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

NMT Stack traces should skip the function that creates the stack trace

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: P4 P4
    • 10
    • 9
    • hotspot

      running NMT:

      java -XX:NativeMemoryTracking=detail <java2demo or something>
      ... wait ...
      jcmd <pid> VM.native_memory detail >out

      In the detailed output, many of the stacktraces start with the function that creates the stack trace. It should start with the second thing in the stack trace so that we get one more frame at the bottom of the list (or top of the stack itself).

      [0xf6c6e7ff] NativeCallStack::NativeCallStack(int, bool)+0x5f
      [0xf66cb395] ChunkPool::allocate(unsigned int, AllocFailStrategy::AllocFailEnum)+0x125
      [0xf66ca15d] Arena::Arena(MemoryType, unsigned int)+0x14d
      [0xf6c0377d] Matcher::Matcher()+0x4d
                                   (malloc=20KB #2)
      [] we want one more frame here and not NativeCallStack!!

            Unassigned Unassigned
            coleenp Coleen Phillimore
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: