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

Segfault in JNIHandleBlock::oops_do()

    XMLWordPrintable

Details

    • b16
    • generic
    • Not verified

    Backports

      Description

        We're seeing intermittent SEGVs in JDKs with some newer GCC versions and combinations of options. It turns out that it's a pretty trivial error which has never been noticed before.

        Thread::oops_do() does this:

        void Thread::oops_do(OopClosure* f, CodeBlobClosure* cf) {
          active_handles()->oops_do(f);

        However, there is a window while a Thread is being constructed when active_handles() is NULL. GC can occur during this time period, and it's a matter of luck that we haven't seen this crash before.

        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-8241501 Segfault in JNIHandleBlock::oops_do()

            • 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-8241560 Segfault in JNIHandleBlock::oops_do()

            • 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-8241652 Segfault in JNIHandleBlock::oops_do()

            • 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-8241774 Segfault in JNIHandleBlock::oops_do()

            • 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-8242087 Segfault in JNIHandleBlock::oops_do()

            • 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-8246684 Segfault in JNIHandleBlock::oops_do()

            • 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-8241543 Segfault in JNIHandleBlock::oops_do()

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

            Activity

              People

                aph Andrew Haley
                aph Andrew Haley
                Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: