在object.finalize()超时10秒后,(最多不大于20s),会触发GC超时关闭JVM
FinalizerDaemon与FinalizerWatchdogDaemon
- FinalizerDaemon守护线程:负责执行object.finalize()与设置FinalizerWatchdogDaemon线程的标志位。
- FinalizerWatchdogDaemon:负责执行超时逻辑,其wait与notify行为被FinalizerDaemon控制。
FinalizerDaemon分析
- gc前卡在这 line: 25
- 唤醒FinalizerWatchdogDaemon线程 line: 30
- 执行object.finalize() line: 33
- 若queue中还有需要finalize的走这里,继续执行第3步 line: 17
- 所有object的finalize全部结束走这里 line: 21
- 设置flag告诉FinalizerWatchdogDaemon 线程 可以wait了 line: 24
private static class FinalizerDaemon extends Daemon {
@UnsupportedAppUsage
private static final FinalizerDaemon INSTANCE = new FinalizerDaemon();
private final ReferenceQueue<Object> queue = FinalizerReference.queue;
private final AtomicInteger progressCounter = new AtomicInteger(0);
@UnsupportedAppUsage
private Object finalizingObject = null;
@Override public void runInternal() {
int localProgressCounter = progressCounter.get();
while (isRunning()) {
try {
// Use non-blocking poll to avoid FinalizerWatchdogDaemon communication
// when busy.
FinalizerReference<?> finalizingReference = (FinalizerReference<?>)queue.poll();
if (finalizingReference != null) {
//4.若queue中还有需要finalize的走这里,继续执行第3步
finalizingObject = finalizingReference.get();
progressCounter.lazySet(++localProgressCounter);
} else {
//5.所有object的finalize全部结束走这里
finalizingObject = null;
progressCounter.lazySet(++localProgressCounter);
//6.设置flag告诉FinalizerWatchdogDaemon线程可以wait了。
FinalizerWatchdogDaemon.INSTANCE.goToSleep();
//1.gc前卡在这
finalizingReference = (FinalizerReference<?>)queue.remove();
finalizingObject = finalizingReference.get();
progressCounter.set(++localProgressCounter);
//2.唤醒FinalizerWatchdogDaemon线程
FinalizerWatchdogDaemon.INSTANCE.wakeUp();
}
//3.执行object.finalize()
doFinalize(finalizingReference);
}
...
}
}
private void doFinalize(FinalizerReference<?> reference) {
FinalizerReference.remove(reference);
Object object = reference.get();
reference.clear();
try {
object.finalize();
} catch (Throwable ex) {
...
} finally {
finalizingObject = null;
}
}
FinalizerWatchdogDaemon分析
- gc前卡在sleepUntilNeeded line: 11
- 进入waitForFinalization line: 16
- 记录FinalizerDaemon的progressCounter line: 30
- 卡在sleepForMillis这里10s line: 32
- 若单个object.finalize()在10s(最多不到20秒)内没有结束,则返回true,超时 line: 36
- 再次确认超时 line:50
- 若一次waitForFinalization10s之后,FinalizerDaemon还没有设置标志位结束, 则继续调用waitForFinalization等待10s 直到所有object都finalize完毕,或者单个object的finalize超时 line: 11
private static class FinalizerWatchdogDaemon extends Daemon {
...
private boolean needToWork = true; // Only accessed in synchronized methods.
@Override public void runInternal() {
while (isRunning()) {
//1.gc前卡在sleepUntilNeeded
//7.若一次waitForFinalization10s之后,FinalizerDaemon还没有设置标志位结束
//则继续掉用waitForFinalization等待10s。
//直到所有object都finalize完毕,或者单个object的finalize超时.
if (!sleepUntilNeeded()) {
// We have been interrupted, need to see if this daemon has been stopped.
continue;
}
//2.进入waitForFinalization
final Object finalizing = waitForFinalization();
if (finalizing != null && !VMRuntime.getRuntime().isDebuggerActive()) {
finalizerTimedOut(finalizing);
break;
}
}
}
private Object waitForFinalization() {
...
finalizerTimeoutMs = VMRuntime.getRuntime().getFinalizerTimeoutMs();
...
//3.记录FinalizerDaemon的progressCounter
long startCount = FinalizerDaemon.INSTANCE.progressCounter.get();
//4.卡在这里10s
if (!sleepForMillis(finalizerTimeoutMs)) {
return null;
}
//5.若单个object.finalize()在10秒(最多不到20秒)内没有结束,则返回true,超时。
if (getNeedToWork() && FinalizerDaemon.INSTANCE.progressCounter.get() == startCount) {
Object finalizing = FinalizerDaemon.INSTANCE.finalizingObject;
sleepForMillis(500);
//6.再次确认超时
if (getNeedToWork()
&& FinalizerDaemon.INSTANCE.progressCounter.get() == startCount) {
return finalizing;
}
}
return null;
}
GC超时与ANR的不同
GC超时与ANR超时的机制设计是不同的。
ANR超时有“埋雷和拆雷”的过程,若在发生ANR之前逻辑完成,会将MessageQueue中“埋下的雷”给删除。
而GC超时机制,每次执行waitForFinalization都会等待10秒(不包括interupt逻辑)。