Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8319548 Unexpected internal name for Filler array klass causes error in VisualVM
  3. JDK-8336961

Release Note: Name Change for Filler Array Objects from `jdk.vm.internal.FillerArray` to `[Ljdk/internal/vm/FillerElement;`

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Delivered
    • Icon: P4 P4
    • 23
    • 21.0.3, 21.0.4-oracle, 22.0.2, 23
    • hotspot
    • gc
    • 21

      One HotSpot virtual machine internal class to indicate an area of dead (unreachable) memory has been renamed to conform to the Java class naming standard to avoid confusing external applications parsing virtual machine class histograms provided by `jmap -histo`.

      There are applications that parse the output of `jmap -histo` which fail when encountering the class `jdk.vm.internal.FillerArray`. In particular, the issue is that this type of filler object represents a flexibly sized range of unreachable memory but is named as if it were a fixed size non-array object. Then, for example, calculating the instance size of these objects from the `jmap -histo` output can result in non-integral instance sizes, confusing applications.

      This problem has been fixed by changing the name of this class to the array-like name `[Ljdk/internal/vm/FillerElement;`.

            tschatzl Thomas Schatzl
            tschatzl Thomas Schatzl
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: