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

Assertion failure "wrong array object size"

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • P4
    • hs10
    • 5.0, 6
    • hotspot
    • None
    • gc
    • 1.4.2
    • b14
    • x86, sparc
    • linux, solaris, solaris_8

    Backports

      Description

        This failure has been seen at least twice in PRT runs.

        # Internal Error (/net/prt-solsparc-q1-2/tmp/PrtBuildDir/workspace/src/share/vm/oops/oop.inline.hpp, 162 [ Patched ]), pid=24097, tid=4
        #
        # Java VM: Java HotSpot(TM) Client VM (20050524083538.jmasa.gc_baseline_4994453b-debug mixed mode)
        #
        # Error: assert(s == klass->oop_size(this),"wrong array object size")

        The above excerpt is from the lastest sighting. It was also reported
        in

        # Java VM: Java HotSpot(TM) Client VM (20050503030401.pb131437.hotspot-debug mixed mode)
        #
        # Error: assert(s == klass->oop_size(this),"wrong array object size")



        ###@###.### 2005-05-24 18:47:33 GMT
        The nightly testing for 1May2007 failed on test gc/ArrayJuggle/Juggle12

        [2007-05-02T04:15:12.45] # Error: assert((s == klass->oop_size(this)) || (UseParNewGC && !UseConcMarkSweepGC && Universe::heap()->is_gc_active()),"wrong array object size")

        Attachments

          Issue Links

            backported by

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-2131196 Assertion failure "wrong array object size"

            • P2 - Crashes, loss of data, severe memory leak.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-2142940 Assertion failure "wrong array object size"

            • P3 - Major loss of function.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-2171783 Assertion failure "wrong array object size"

            • P3 - Major loss of function.
            • Resolved

            Backport - A issue that is required to port a Bug or Feature into another product release. This issue type is generally associated with the main Bug/Feature to represent each individual release of the port. JDK-2176936 Assertion failure "wrong array object size"

            • P3 - Major loss of function.
            • Closed
            relates to

            Bug - A problem which impairs or prevents the functions of the product. JDK-6288235 atg and tomcat apps failed in mustang b41

            • P4 - Minor loss of function, or other problem where easy workaround is present.
            • Closed

            Activity

              People

                ysr Y. Ramakrishna
                jmasa Jon Masamitsu (Inactive)
                Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:
                  Imported:
                  Indexed: