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

"assert(thread != NULL) failed: just checking" due to Thread::current() and JNI pthread interaction

    XMLWordPrintable

Details

    • b10
    • x86_64
    • generic

    Backports

      Description


        JNI code is using pthread_key_create with a destructor to detach the thread from the JVM when the thread is exiting.

        This solution works well when running on Solaris or a 32 bit JVM on Linux, but when run on 64 bit JVM on Linux the threads hang when detaching.

        For 64 bit Linux the JVM is also using the pthread_key_create, to store the

        Thread::current() value in a thread local storage.

        Since the thread local storage containing the thread pointer is erased (by pthread) before the JNI destructor runs, we run detachCurrentThread on a thread that has NULL as current thread.

        With a product build this breaks locks/monitors, and the threads hang. With a debug build an assert in Thread::current() is hit instead.

        Everything works if detachCurrentThread is called from the main logic instead.

        Attachments

          1. callback_jni.tar.gz
            3 kB
          2. runMac.sh
            0.6 kB
          3. thread_pointer.patch
            0.7 kB

          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-8045389 "assert(thread != NULL) failed: just checking" due to Thread::current() and JNI pthread interaction

            • 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-8050335 "assert(thread != NULL) failed: just checking" due to Thread::current() and JNI pthread interaction

            • 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-8053308 "assert(thread != NULL) failed: just checking" due to Thread::current() and JNI pthread interaction

            • 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-8057298 "assert(thread != NULL) failed: just checking" due to Thread::current() and JNI pthread interaction

            • 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-8060865 "assert(thread != NULL) failed: just checking" due to Thread::current() and JNI pthread interaction

            • 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-8039740 "assert(thread != NULL) failed: just checking" due to Thread::current() and JNI pthread interaction

            • 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-8039907 "assert(thread != NULL) failed: just checking" due to Thread::current() and JNI pthread interaction

            • 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-8049869 "assert(thread != NULL) failed: just checking" due to Thread::current() and JNI pthread interaction

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

            Bug - A problem which impairs or prevents the functions of the product. JDK-8025568 Crash in VM starting NetBeans 7.3.1 on Ubuntu 13.04 with Java 8 EA build 106

            • P1 - Blocks development and/or testing work, production could not run.
            • Resolved

            Bug - A problem which impairs or prevents the functions of the product. JDK-8301570 Test runtime/jni/nativeStack/ needs to detach the native thread

            • P3 - Major loss of function.
            • Resolved

            Bug - A problem which impairs or prevents the functions of the product. JDK-8156708 Intermittent hangs/timeouts on SPARC in G1 since 9-b99

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

            Enhancement - null JDK-8057761 [TESTBUG] Need a test to cover JDK-8033696

            • P3 - Major loss of function.
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. JDK-8154715 Missing destructor and/or TLS clearing calls for terminating threads

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

            Activity

              People

                aeriksso Andreas Eriksson (Inactive)
                asaha Abhijit Saha
                Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: