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

Possible race condition after JDK-6664509

    XMLWordPrintable

Details

    • b02
    • other
    • other
    • Not verified

    Backports

      Description

        On 2/1/13 8:11 AM, Mandy Chung wrote:

        By code inspection, however, I concur that there is a timing race there that a logger can
        be GC'ed where a logger exists where being queried and immediately being gc'ed after that.
        I don't think Licensee's proposed 1-line fix is a completed fix though.

        LogManager.java L 633-635
                    if (!manager.addLogger(result) && result.getHandlers().length == 0) {
                        // if logger already exists but handlers not set
                        final Logger l = manager.getLogger(name);
                        final Logger logger = result;

        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-8007424 Possible race condition after JDK-6664509

            • 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-8007413 Possible race condition after JDK-6664509

            • 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-8007421 Possible race condition after JDK-6664509

            • 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-8007422 Possible race condition after JDK-6664509

            • 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-8007423 Possible race condition after JDK-6664509

            • 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-8007943 Possible race condition after JDK-6664509

            • 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-8008720 Possible race condition after JDK-6664509

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

            Activity

              People

                mchung Mandy Chung
                dkorbel David Korbel (Inactive)
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: