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

LogManager unecessarily calls JavaAWTAccess from within a critical section

    XMLWordPrintable

Details

    Backports

      Description

        A deadlock involving AppContext, EventQueue, and LogManager.getUserContext() has been reported by JDK-8065709.
        The traces show that LogManager.getUserContext() calls JavaAWTAccess - and henceforth AppContext.getAppContex() from within a synchronized block - when in fact it could be called before entering the critical section.

        Note: This change is not sufficient to completely remove the deadlock: if the LogManager has not been initialized yet, then ensureLogManagerInitialized will end up calling LogManager.getUserContext() from within another critical section, with potentially the same effect. In this second case removing this second critical section is not an option.

        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-8068109 LogManager unecessarily calls JavaAWTAccess from within a critical section

            • 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-8069974 LogManager unecessarily calls JavaAWTAccess from within a critical section

            • 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-8071323 LogManager unecessarily calls JavaAWTAccess from within a critical section

            • 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-8071612 LogManager unecessarily calls JavaAWTAccess from within a critical section

            • 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-8084716 LogManager unecessarily calls JavaAWTAccess from within a critical section

            • 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-8066907 LogManager unecessarily calls JavaAWTAccess from within a critical section

            • P2 - Crashes, loss of data, severe memory leak.
            • 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-8071593 LogManager unecessarily calls JavaAWTAccess from within a critical section

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

            Bug - A problem which impairs or prevents the functions of the product. JDK-8065709 Deadlock in awt/logging apparently introduced by 8019623

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

            Bug - A problem which impairs or prevents the functions of the product. JDK-8065709 Deadlock in awt/logging apparently introduced by 8019623

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

            Bug - A problem which impairs or prevents the functions of the product. JDK-8071591 [TESTBUG] java/util/logging/LogManagerAppContextDeadlock.java test started to fail due to JDK-8065991

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

            Bug - A problem which impairs or prevents the functions of the product. JDK-8019623 Lack of synchronization in AppContext.getAppContext()

            • P3 - Major loss of function.
            • Resolved

            Activity

              People

                dfuchs Daniel Fuchs
                dfuchs Daniel Fuchs
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: