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

AWT hang occurs when sequenced events arrive out of sequence in multiple AppContexts.

    XMLWordPrintable

Details

    • b20

    Backports

      Description

        This issue is caused due to the fix for JDK-8152974. In the case of Applets, multiple AppContexts are created and the events are waiting for the wrong event id to arrive, which never comes (due to the fix mentioned earlier).

        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-8217439 AWT hang occurs when sequenced events arrive out of sequence in multiple AppContexts.

            • 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-8217497 AWT hang occurs when sequenced events arrive out of sequence in multiple AppContexts.

            • 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-8218741 AWT hang occurs when sequenced events arrive out of sequence in multiple AppContexts.

            • 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-8219649 AWT hang occurs when sequenced events arrive out of sequence in multiple AppContexts.

            • 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-8221628 AWT hang occurs when sequenced events arrive out of sequence in multiple AppContexts.

            • 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-8221637 AWT hang occurs when sequenced events arrive out of sequence in multiple AppContexts.

            • 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-8221873 AWT hang occurs when sequenced events arrive out of sequence in multiple AppContexts.

            • 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-8221955 AWT hang occurs when sequenced events arrive out of sequence in multiple AppContexts.

            • 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-8224413 AWT hang occurs when sequenced events arrive out of sequence in multiple AppContexts.

            • 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-8219444 AWT hang occurs when sequenced events arrive out of sequence in multiple AppContexts.

            • 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-8221678 AWT hang occurs when sequenced events arrive out of sequence in multiple AppContexts.

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

            Bug - A problem which impairs or prevents the functions of the product. JDK-8202374 AWT hang in Web Start applicatioins in 8u-dev

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

            Bug - A problem which impairs or prevents the functions of the product. JDK-8242904 Gui hang up if using jdk1.8.0_201 due to AWT EventQueue hang

            • P3 - Major loss of function.
            • Open

            Bug - A problem which impairs or prevents the functions of the product. JDK-8152974 AWT hang occurrs when sequenced events arrive out of sequence

            • P3 - Major loss of function.
            • Resolved

            Bug - A problem which impairs or prevents the functions of the product. JDK-8211435 Exception in thread "AWT-EventQueue-1" java.lang.IllegalArgumentException: null source

            • P3 - Major loss of function.
            • Resolved

            Activity

              People

                mbalao Martin Balao
                kaddepalli Krishna Addepalli
                Votes:
                1 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: