c# - 析构函数不能保证完成运行吗？

Question

析构函数很奇怪。我试图通过使用“智能”引用管理来消除使用一次性模式的需要，确保垃圾收集器可以在正确的时间收集对象。在我的一个析构函数中，我不得不等待来自另一个对象的事件，但我注意到它没有。应用程序简单地关闭并且析构函数在执行过程中终止。 我希望始终允许析构函数完成运行，但正如以下测试表明的那样。

using System;
using System.Diagnostics;
using System.Threading;


namespace DestructorTest
{
    class Program
    {
        static void Main( string[] args )
        {
            new DestructorTest();
            new LoopDestructorTest();
            using ( new DisposableTest() ) { }
        }
    }

    class DestructorTest
    {
        ~DestructorTest()
        {
            // This isn't allowed to finish.
            Thread.Sleep( 10000 );
        }       
    }

    class LoopDestructorTest
    {
        ~LoopDestructorTest()
        {           
            int cur = 0;
            for ( int i = 0; i < int.MaxValue; ++i )
            {
                cur = i;
            }
            // This isn't allowed to finish.
            Debug.WriteLine( cur );
        }
    }

    class DisposableTest : IDisposable
    {
        public void Dispose()
        {
            // This of course, is allowed to finish.
            Thread.Sleep( 10000 );
        }
    }
}

那么，析构函数不能保证完成运行吗？

Answer 1

So, aren't destructors guaranteed to finish running?

没有。据我所知，当进程终止时，它给终结器几秒钟的时间来执行，但随后突然终止了进程。您不会想要一个糟糕的终结器来阻止进程完成，对吗？

您应该将终结视为“尽力而为”的清理 - 特别是，它不会发生在整个系统突然关闭的情况下，例如 BSOD 或断电。

编辑:我发现了一些形式为 blog post from Joe Duffy 的伪文档:

If a lock was orphaned in the process of stopping all running threads, then, the shutdown code path will fail to acquire the lock. If these acquisitions are done with non-timeout (or long timeout) acquires, a hang will ensue. To cope with this (and any other sort of hang that might happen), the CLR annoints a watchdog thread to keep an eye on the finalizer thread. Although configurable, by default the CLR will let finalizers run for 2 seconds before becoming impatient; if this timeout is exceeded, the finalizer thread is stopped, and shutdown continues without draining the rest of the finalizer queue.