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

VMThread issues and cleanup

    XMLWordPrintable

Details

    • b18

    Description

      The VM thread code a few issue:
      - It can create an extra safepoint directly after a safepoint.
      - It's not safe for a non-JavaThread to add safepoint to queue while GC do oops do.
      - The exposure of the vm operation is dangerous if it's a handshake.
      - The code is a hornets nest with the repetition of checks and branches

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. JDK-8253833 mutexLocker assert_locked_or_safepoint should not access VMThread state from non-VM-thread

          • P3 - Major loss of function.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JDK-8253778 ShenandoahSafepoint::is_at_shenandoah_safepoint should not access VMThread state from other threads

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

          Bug - A problem which impairs or prevents the functions of the product. JDK-8253794 TestAbortVMOnSafepointTimeout never timeouts

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

          Enhancement - null JDK-8212108 SafepointSynchronizer never ending counter (big enough)

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

          Commit Commit openjdk/jdk/431338bc

          Review Review openjdk/jdk/228

          Activity

            People

              rehn Robbin Ehn
              rehn Robbin Ehn
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: