我记得我们曾经使用过的一个MFC应用程序.它使用了多线程，当主线程试图退出时，子线程仍然存在，它们引用的内存变为Null并最终使应用程序崩溃.我们重新排序线程的逻辑和调用 修复问题的顺序.这很像您的情况，但是这次是关于CLR类li​​b的事情.我认为人们很难根据您发布的信息来找到其崩溃的根本原因.也许我们需要有关该体系结构的更多信息 您的应用程式或应用程式的逻辑.

I recall one MFC app we used to work on. It used multiple-threads, and when the Main thread try to exit, the sub-threads are still alive, the memory they referred turned to Null and make the app crash after all. We reorder the threads' logic and the call sequences to fix it. This is much like your case but this time is something about CLR class lib. I don't think it's easy for people to locate the root cause why it crashes based on the information you posted. Maybe we need more info about the architecture of your app or some logic of it.