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

GC-a-lot feature should be NoHandleMark-aware

    Details

    • Type: Bug
    • Status: Open
    • Priority: P4
    • Resolution: Unresolved
    • Affects Version/s: hs15
    • Fix Version/s: tbd
    • Component/s: hotspot
    • Labels:
      None
    • Subcomponent:
      gc
    • Understanding:
      Cause Known
    • Introduced In Build:
      1.4.2
    • Introduced In Version:
    • CPU:
      generic
    • OS:
      generic

      Description

      There are portions of execution of threads during which they vow not to
      allocate in the heap or to create handles. These are specific small
      portions of code that are understood to not invoke GC or safepoints
      on their own so the thread can operate at full speed, and as such are
      marked by a NoHandleMark() or NoSafepointVerifier() scope.
      It appears as though the GC-a-lot feature may occasionally run
      afoul of these blocks, so the interaction of these two should
      be investigated and cleaned up.

      See comments section for more data.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                ysr Y. Ramakrishna
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Imported:
                  Indexed: