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

TestInstanceKlassSize failing on linuxppc64 and linuxppc64le

XMLWordPrintable

      The test serviceability/sa/TestInstanceKlassSize.java is failing on linuxppc64 and linuxppc64le with the following symptom:
      java.lang.RuntimeException: The size computed by SA for java.lang.Object does not match.: expected true, was false
      at jdk.test.lib.Asserts.fail(Asserts.java:594)
      at jdk.test.lib.Asserts.assertTrue(Asserts.java:486)
      at TestInstanceKlassSize.startMeWithArgs(TestInstanceKlassSize.java:139)
      at TestInstanceKlassSize.main(TestInstanceKlassSize.java:180)
      at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
      at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      at java.base/java.lang.reflect.Method.invoke(Method.java:564)
      at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:127)
      at java.base/java.lang.Thread.run(Thread.java:830)

      The test retrieves the size of Java classes by 2 different APIs and expects the result to be equal:
      - SA reports the size of the reserved memory. Rounded up to a multiple of 16 on PPC64.
      - Jcmd GC.class_stats reports the size of the space needed for a number of 8 Byte blocks. (The number is from an internal statistic.)
      So there may be a difference of 8 Bytes on platforms which reserve memory 16 Byte wise.

        There are no Sub-Tasks for this issue.

            Unassigned Unassigned
            clanger Christoph Langer
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: