WPF application run for a period of time to collapse, have global exception handling, but couldn't catch,
In the Windows event manager to find the following records, bosses analyze

Application: PCDemo. Exe
Framework version: v4.0.30319
Note: untreated anomaly, process terminates,
An abnormal information: code for c0000005, exception address is 6 a428c61
Stack:
In the System. Windows. Forms. UnsafeNativeMethods. IntDestroyWindow (System. The Runtime. InteropServices. HandleRef)
In the System. Windows. Forms. UnsafeNativeMethods. DestroyWindow (System. The Runtime. InteropServices. HandleRef)
In the System. Windows. Forms. NativeWindow. DestroyHandle ()
In the System. Windows. Forms. Control. DestroyHandle ()
In the System. Windows. Forms. Control. The Dispose (Boolean)
In the System. Windows. Forms. Integration. WinFormsAdapter. The Dispose (Boolean)
In System.ComponentModel.Com ponent. The Dispose ()
In the System. Windows. Forms. Integration. WindowsFormsHost. DestroyWindowCore (System. The Runtime. InteropServices. HandleRef)
In the System. Windows. Interop. HwndHost. DestroyWindow ()
In the System. Windows. Interop. HwndHost. The Dispose (Boolean)
In the System. Windows. Forms. Integration. WindowsFormsHost. The Dispose (Boolean)
In the System. Windows. Interop. HwndHost + WeakEventDispatcherShutdown. OnShutdownFinished (System. Object, System. EventArgs)
In the System. The EventHandler. Invoke (System. Object, System. EventArgs)
In the System. Windows. Threading. Dispatcher. ShutdownImplInSecurityContext System. (Object)
In the System. The Threading. -- an optional ExecutionContext. RunInternal (System) Threading) -- an optional ExecutionContext, System. Threading. ContextCallback, System. Object, Boolean)
In the System. The Threading. -- an optional ExecutionContext. Run (System) Threading) -- an optional ExecutionContext, System. Threading. ContextCallback, System. Object, Boolean)
In the System. The Threading. -- an optional ExecutionContext. Run (System) Threading) -- an optional ExecutionContext, System. Threading. ContextCallback, System. Object)
In Ms. Internal. CulturePreservingExecutionContext. Run (MS) Internal) CulturePreservingExecutionContext, System. Threading. ContextCallback, System. Object)
In the System. Windows. Threading. Dispatcher. ShutdownImpl ()
In the System. Windows. Threading. Dispatcher. PushFrameImpl (System. Windows. Threading. DispatcherFrame)
In the System. Windows. Threading. Dispatcher. PushFrame (System. Windows. Threading. DispatcherFrame)
In the System. Windows. Application. RunDispatcher (System. Object)
In the System. Windows. Application. RunInternal (System. Windows. Windows)
In the System. Windows. Application. The Run (System. Windows. Windows)
In PCDemo. App. The Main ()

CodePudding user response:

There is also a

Error application name: PCDemo. Exe version: 1.0.0.0, timestamp: 0 xf11baba3
Error module name: PM101DA. DLL version: 4.1.404.6, timestamp: 0 x5f372c65
Exception code: 0 xc0000005
Error offset: 0 x00008c61
Error process ID: 0 xe508
Error application startup time: 0 x01d6ea837df46e54
Error application path: C: \ Release \ PCDemo
Error module path: C: \ Release \ Dll \ PM101DA Dll
The report ID: a230aef2 - e56c - 496 - d - b6ea - 6 d3146551283
Wrong package name:

CodePudding user response:

Program using the Winform PictureBox handle, PM101DA. DLL by handle in PictureBox displayed on the screen

CodePudding user response:

Form out do not make clear unmanaged, cause PM101DA. During his visit to the backstage to refresh the DLL, visited released handle

CodePudding user response:

reference wanghui0380 reply: 3/f

exit Form do not make clear unmanaged, cause PM101DA. During his visit to the backstage to refresh the DLL, visited released handle

this exception capture less than? , I have to do a global exception handling in contains a PictureBox Usercontrol Unloaded when do the cleaning work, when does PM101DA. DLL internal problems?

CodePudding user response:

This exception to SEH exception (i.e., no abnormalities are mapping), the default cannot capture,
Unless you show capture, question on here to clear his baidu "c # SEHException
"

CodePudding user response:

reference 5 floor wanghui0380 reply:

this exception to SEH exception (i.e., no abnormalities are mapping), the default cannot capture,
Unless you show capture, question on here to clear his baidu "c # SEHException"

ok, thank you, I'll check it

CodePudding user response:

Ps: it is recommended that in the Dispose to do release action, such as to stop the recording, stop rendering such action,
Can also be to handle ascension as a member of the class, this class at least not happen before the Dispose abnormal

CodePudding user response:

1 is how to capture the global variable?
2 use the unmanaged function?