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

CMS: BOT walkers can fall into object allocation and initialization cracks

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • P3
    • hs19
    • hs16, hs17, 1.4.2, 1.4.2_12, 5.0u7, 5.0u17, 5.0u19, 6u13, 6u14, 6u15, 6u16, 6u18, 6u19, 6u20, 6u21
    • hotspot
    • gc
    • 1.4.2
    • b06
    • generic, x86, sparc
    • generic, solaris, solaris_10
    • Not verified

    Backports

      Description

        BOT walkers can sometimes observe allocated-but-not-yet-fully initialized
        objects, which can cause crashes during GC (both the concurrent as well
        as the stop-world phases, with the latter much more likely).

        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-2193018 CMS: BOT walkers can fall into object allocation and initialization cracks

            • 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-2197585 CMS: BOT walkers can fall into object allocation and initialization cracks

            • 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-2197879 CMS: BOT walkers can fall into object allocation and initialization cracks

            • 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-2199780 CMS: BOT walkers can fall into object allocation and initialization cracks

            • 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-2198036 CMS: BOT walkers can fall into object allocation and initialization cracks

            • P3 - Major loss of function.
            • Closed

            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-2204493 CMS: BOT walkers can fall into object allocation and initialization cracks

            • P3 - Major loss of function.
            • Closed

            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-2204494 CMS: BOT walkers can fall into object allocation and initialization cracks

            • P3 - Major loss of function.
            • Closed
            duplicates

            Bug - A problem which impairs or prevents the functions of the product. JDK-6872049 CMS: Failure in CompactibleFreeListSpace::block_size from ::block_start_unsafe()

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

            Bug - A problem which impairs or prevents the functions of the product. JDK-6996061 CMS: Crash at CompactibleFreeListSpace::forward

            • P3 - Major loss of function.
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. JDK-6858243 CMS: Fencing needed for hw with weak memory model

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

            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-2186462 CMS: Failure in CompactibleFreeListSpace::block_size from ::block_start_unsafe()

            • P3 - Major loss of function.
            • Closed

            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-2187366 CMS: Failure in CompactibleFreeListSpace::block_size from ::block_start_unsafe()

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

            Bug - A problem which impairs or prevents the functions of the product. JDK-6912621 iCMS: Error: assert(_markBitMap.isMarked(addr + 1),"Missing Printezis bit?")

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

            Bug - A problem which impairs or prevents the functions of the product. JDK-6977970 CMS: concurrentMarkSweepGeneration.cpp:7947 assert(addr <= _limit) failed: sweep invariant

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

            Bug - A problem which impairs or prevents the functions of the product. JDK-6565513 CMS: assert at blockOffsetTable.cpp:39: assert(left_blk_size > 0,"Should be positive")

            • P3 - Major loss of function.
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. JDK-6978533 CMS: Elide BOT update asserts until 6977974 is fixed correctly

            • P3 - Major loss of function.
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. JDK-6977974 CMS: blockOffsetTable.hpp:187 assert(!reducing || _offset_array[i] >= offset) failed: Not reducing

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

            Bug - A problem which impairs or prevents the functions of the product. JDK-6973570 OrderAccess::storestore() scales poorly on multi-socket x64 and sparc: cache-line ping-ponging

            • P3 - Major loss of function.
            • Closed

            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-2197146 CMS: concurrentMarkSweepGeneration.cpp:7947 assert(addr <= _limit) failed: sweep invariant

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

            Activity

              People

                ysr Y. Ramakrishna
                ysr Y. Ramakrishna
                Votes:
                0 Vote for this issue
                Watchers:
                11 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:
                  Imported:
                  Indexed: