析构异常引发崩溃问题分析.docx

退出线程时由于析构错误引发的崩溃! Problem: Fatal error thread exit if FLS callback not freed kb/2754614 By 唔該正常D 在退出进程之前崩溃,dump 显示系统尝试调用一个已经卸载了DLL 里的函数,引发崩溃现象:win7/win2003 下,程序在关机时崩溃,有DUMP 生成, 错误代码,COM 组件释放有问题 Cxx::~Cxx() { if (NULL != m_pInterfaceXX) { delete m_pInterfaceXX; m_pInterfaceXX = NULL; } } 正确代码应该为 Cxx::~Cxx() { if (NULL != m_pInterfaceXX) { m_pInterfaceXX-Release(); } } A C++ DLL statically linked to CRT may cause a fatal error at thread exit if the DLL load or A C++ DLL statically linked to CRT may cause a fatal error at thread exit if the DLL load or unload sequence is interrupted by an unhandled exception. A process may crash at thread exit with an Access Violation exception (0xC0000005, EXCEPTION_ACCESS_VIOLATION) if it had dynamically loaded (such as by calling LoadLibrary()) a native C++ DLL that was statically linked with C Runtime, and the DLL generated an unhandled exception during its initialization or shutdown. During the CRT startup or shutdown (such as during DLL_PROCESS_ATTACH or DLL_PROCESS_DETACH in DllMain(), or in the constructor or destructor of a global/static C++ object), if the DLL generates a fatal error that is unhandled, the LoadLibrary call just swallows the exception and returns with NULL. When the DLL load or unload fails, some error codes you may observe include: ? ERROR_NOACCESS (998) or EXCEPTION_ACCESS_VIOLATION (0xC0000005, 0n3221225477) ? EXCEPTION_INT_DIVIDE_BY_ZERO (0xC0000094, 0n3221225620) ? ERROR_STACK_OVERFLOW (1001) or EXCEPTION_STACK_OVERFLOW (0xC00000FD, 0n3221225725) ? C++ exception (0xE06D7363, 0n3765269347) ? ERROR_DLL_INIT_FAILED (0x8007045A) This library startup or shutdown failure usually is not observed until the calling thread is about to exit, in the form of a deadly Access Violation exception with a similar call stack as below: Unloaded_TestDll.dll+0x1642 ntdll!RtlProcessFlsData+0x57 ntdll!LdrShutdownProcess+0xbd ntdll!RtlExitUserProcess+0x74 kernel32!ExitProcessStub+0x12 TestExe! crtExitProcess+0x17 TestExe!doexit