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

Shenandoah: pacer should not affect interrupt status

    XMLWordPrintable

Details

    • gc
    • b27
    • Not verified

    Backports

      Description

        This was originally found by Aditya Mandaleeka when running sh/jdk11 tests. It seems to reproduce as the very rare timeout in java/security/Provider/GetServiceRace.java test. The underlying reason is that pacer does this:

           JavaThread::current()->sleep(cur);

        ...which in turn checks and *clears* the interrupt status in the guts of OS code:

            if (os::is_interrupted(thread, true)) { // "true" means clear interrupt status
              return OS_INTRPT;
            }

        And that interferes with interrupt status of Java thread. This is incorrect.

        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-8248083 Shenandoah: pacer should not affect interrupt status

            • 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-8248953 Shenandoah: pacer should not affect interrupt status

            • 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-8249108 Shenandoah: pacer should not affect interrupt status

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

            Bug - A problem which impairs or prevents the functions of the product. JDK-8247474 Shenandoah: Windows build warning after JDK-8247310

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

            Enhancement - null JDK-8247367 Shenandoah: pacer should wait on lock instead of exponential backoff

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

            Activity

              People

                shade Aleksey Shipilev
                shade Aleksey Shipilev
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: