java.util.concurrent.TimeoutException: java.util.regex.Matcher.finalize() timed out after 120 second

最近在App错误日志上看到这样一个错误：

java.util.concurrent.TimeoutException: java.util.regex.Matcher.finalize() timed out after 120 seconds
    at java.lang.Daemons$Daemon.isRunning(Daemons.java:89)
    at java.lang.Daemons$FinalizerDaemon.run(Daemons.java:190)
    at java.lang.Thread.run(Thread.java:818)

1.问题分析：
由于在一些设备上UI和Render线程的Nice优先级值都是负数，而该线程的Nice值一般情况下是0，也就是默认值。在UI等其他线程都繁忙的时候，finalize的回收并不会很快，这样就会导致内存回收变慢，进一步影响到整体的性能。特别是很多低性能的设备，更加容易暴露这方面的问题。

2.初识FinalizerWatchdogDaemon
2.1 FinalizerWatchdogDaemon的意义：
FinalizerWatchdogDaemon的类注释写的很清楚.当一个实例的finalizer函数,花费了超过MAX_FINALIZATION_MILLIS时间(默认为10秒).将被认定finalizer卡死,此时,FinalizerWatchdogDaemon将会让VM退出.

   /**
     * The watchdog exits the VM if the finalizer ever gets stuck. We consider
     * the finalizer to be stuck if it spends more than MAX_FINALIZATION_MILLIS
     * on one instance.
     */
    private static class FinalizerWatchdogDaemon extends Daemon {
        private static final FinalizerWatchdogDaemon INSTANCE = new FinalizerWatchdogDaemon();

        FinalizerWatchdogDaemon() {
            super("FinalizerWatchdogDaemon");
        }

        @Override public void run() {
        ...
        }
}

2.2 TimeoutException在哪里抛出的？

private static void finalizerTimedOut(Object object) {
            // The current object has exceeded the finalization deadline; abort!
            String message = object.getClass().getName() + ".finalize() timed out after "
                    + (MAX_FINALIZE_NANOS / NANOS_PER_SECOND) + " seconds";
            Exception syntheticException = new TimeoutException(message);
            // We use the stack from where finalize() was running to show where it was stuck.
            syntheticException.setStackTrace(FinalizerDaemon.INSTANCE.getStackTrace());
            Thread.UncaughtExceptionHandler h = Thread.getDefaultUncaughtExceptionHandler();
            // Send SIGQUIT to get native stack traces.
            try {
                Os.kill(Os.getpid(), OsConstants.SIGQUIT);
                // Sleep a few seconds to let the stack traces print.
                Thread.sleep(5000);
            } catch (Exception e) {
                System.logE("failed to send SIGQUIT", e);
            } catch (OutOfMemoryError ignored) {
                // May occur while trying to allocate the exception.
            }
            if (h == null) {
                // If we have no handler, log and exit.
                System.logE(message, syntheticException);
                System.exit(2);
            }
            // Otherwise call the handler to do crash reporting.
            // We don't just throw because we're not the thread that
            // timed out; we're the thread that detected it.
            h.uncaughtException(Thread.currentThread(), syntheticException);
        }

3.问题解析
从GC来看.JAVA在内存回收的时候.并不是马上将对象销毁,而是放入到一个队列中,由FinalizerDaemon(析构守护线程)调用他们的finalize方法,再被回收,所以当FinalizerDaemon回收过程中.超过10秒,FinalizerWatchdogDaemon线程就会抛出TimeoutException XXX.finalize() timed out after 10 seconds.

4.怎样避免这种异常的出现
首先，该异常由Java虚拟机在回收对象时所抛出，在我们的代码层是无法捕获的。应该尽量减少在短时间内频繁创建对象，以导致java虚拟机频繁GC。