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

EventDispatchThread shouldn't be reinitialized for disposed AppContexts

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • P4
    • 7
    • 7
    • client-libs
    • b74
    • generic
    • generic
    • Verified

    Description

      This issue is reported at java.net forum:

      http://forums.java.net/jive/thread.jspa?messageID=333410

      Sometimes the following exception is observed in Java Console when applet is being destroyed:

      java.lang.IllegalThreadStateException: forbid thread creation in disposed TG
      at sun.plugin.security.ActivatorSecurityManager.checkAccess(Unknown Source)
      at java.lang.ThreadGroup.checkAccess(Unknown Source)
      at java.lang.Thread.init(Unknown Source)
      at java.lang.Thread.<init>(Unknown Source)
      at java.awt.EventDispatchThread.<init>(Unknown Source)
      at java.awt.EventQueue$1.run(Unknown Source)
      at java.security.AccessController.doPrivileged(Native Method)
      at java.awt.EventQueue.initDispatchThread(Unknown Source)
      at java.awt.EventQueue.postEventPrivate(Unknown Source)
      at java.awt.EventQueue.postEvent(Unknown Source)
      at java.awt.EventQueue.invokeAndWait(Unknown Source)
      at sun.applet.AppletPanel.run(Unknown Source)
      at java.lang.Thread.run(Unknown Source)

      It's clear that it's thrown when AWT tries to create a new EventDispatchThread instance for disposed AppContext.

      Attachments

        Issue Links

          Activity

            People

              art Artem Ananiev (Inactive)
              art Artem Ananiev (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                Imported:
                Indexed: