抛出异常时EDT是否重新启动？

Question

（下面的示例代码是独立且可运行的，您可以尝试一下，它不会使您的系统崩溃:)

Tom Hawtin 在这里评论了这个问题：为什么人们在事件队列上运行 Java GUI

：

EDT 不太可能崩溃。 EDT 调度中抛出的未经检查的异常被捕获、转储并且线程继续。

有人可以解释一下这里发生了什么吗（每次单击“抛出未经检查的异常” 按钮时） ，有意执行除以零）：

import javax.swing.*;
import java.awt.event.ActionEvent;
import java.awt.event.ActionListener;
import java.awt.event.WindowAdapter;
import java.awt.event.WindowEvent;

public class CrashEDT extends JFrame {

    public static void main(String[] args) {
        final CrashEDT frame = new CrashEDT();
        frame.addWindowListener(new WindowAdapter() {
            public void windowClosing( WindowEvent e) {
                System.exit(0);
            }
        });
        final JButton jb = new JButton( "throw an unchecked exception" );
        jb.addActionListener( new ActionListener() {
            public void actionPerformed( ActionEvent e ) {
                System.out.println( "Thread ID:" + Thread.currentThread().getId() );
                System.out.println( 0 / Math.abs(0) );
            }
        } );
        frame.add( jb );
        frame.setSize(300, 150);
        frame.setVisible(true);
    }

}

我收到以下消息（这是我所期望的）：

Exception in thread "AWT-EventQueue-0" java.lang.ArithmeticException: / by zero

对我来说，这是一个未经检查的异常，对吧？

您可以看到，每次触发崩溃时，线程 ID 都会递增。

那么，每次抛出未经检查的异常时，EDT 都会自动重新启动吗？还是像 Tom Hawtin 评论的那样，未经检查的异常“被捕获、转储，线程继续运行”？

这是怎么回事？

Answer 1

有趣的问题。我本以为异常被捕获并且线程继续，但经过一些研究后我不太确定。

我用一个收集了所有“看到的”awt 线程的程序扩展了你的程序

Set<Thread> seenAwtThreads = new HashSet<Thread>();

，每次单击“抛出异常”按钮时，集合的大小都会增加，这似乎表明在出现异常情况时会初始化一个新线程。例外。

最后我在EventDispatchThread的run实现中找到了这样的注释：

/*
 * Event dispatch thread dies in case of an uncaught exception. 
 * A new event dispatch thread for this queue will be started
 * only if a new event is posted to it. In case if no more
 * events are posted after this thread died all events that 
 * currently are in the queue will never be dispatched.
 */

完整的run方法的实现如下所示：

public void run() {
    try {
        pumpEvents(new Conditional() {
            public boolean evaluate() {
                return true;
            }
        });     
    } finally {
        /*
         * This synchronized block is to secure that the event dispatch 
         * thread won't die in the middle of posting a new event to the
         * associated event queue. It is important because we notify
         * that the event dispatch thread is busy after posting a new event
         * to its queue, so the EventQueue.dispatchThread reference must
         * be valid at that point.
         */
        synchronized (theQueue) {
            if (theQueue.getDispatchThread() == this) {
                theQueue.detachDispatchThread();
            }
            /*
             * Event dispatch thread dies in case of an uncaught exception. 
             * A new event dispatch thread for this queue will be started
             * only if a new event is posted to it. In case if no more
             * events are posted after this thread died all events that 
             * currently are in the queue will never be dispatched.
             */
            /*
             * Fix for 4648733. Check both the associated java event
             * queue and the PostEventQueue.
             */
            if (theQueue.peekEvent() != null || 
                !SunToolkit.isPostEventQueueEmpty()) { 
                theQueue.initDispatchThread();
            }
            AWTAutoShutdown.getInstance().notifyThreadFree(this);
        }
    }
}

Answer 2

作为参考，“此机器的特定行为 取决于实现。”例如，线程 ID 在我的平台上保持不变。最终效果，在 AWT 线程问题 是“当至少有一个可显示组件时，JVM 将不会退出”。

Answer 3

有一个默认的 UncaughtExceptionHandler在事件调度线程上设置，它将异常打印到 System.out，然后在线程中继续。