J
Jy_13
Guest
Hi,
I'm working on a legacy product, which loads and unloads one of our DLLs (say DLL A) quite a few times during a particular workflow.
While it successfully loads/unloads DLL A multiple times, it fails at one point with an Access Violation error. We get no further clues, since the application just crashes.
The Windows Event Viewer gives me this information:
Faulting application name: MyApp.exe, version: 8.10.0.651, time stamp: 0x5cd12bdb
Faulting module name: clr.dll, version: 4.7.3394.0, time stamp: 0x5c537182
Exception code: 0xc0000005
Fault offset: 0x0045510d
Faulting process id: 0x20a0
Faulting application start time: 0x01d504a5b280527f
Faulting application path: C:\Users\I_SDU\source\Workspaces\MyApp\build\Debug\x86\MyApp.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
Report Id: a74cfc6e-451a-45be-b060-e9203f56d580
Faulting package full name:
Faulting package-relative application ID:
It is mostly C++/ MFC code, and surprisingly the Faulting module is clr.dll. Not sure what is going wrong.
Appreciate any inputs on how to resolve this crash issue.
TIA,
Jy
Continue reading...
I'm working on a legacy product, which loads and unloads one of our DLLs (say DLL A) quite a few times during a particular workflow.
While it successfully loads/unloads DLL A multiple times, it fails at one point with an Access Violation error. We get no further clues, since the application just crashes.
The Windows Event Viewer gives me this information:
Faulting application name: MyApp.exe, version: 8.10.0.651, time stamp: 0x5cd12bdb
Faulting module name: clr.dll, version: 4.7.3394.0, time stamp: 0x5c537182
Exception code: 0xc0000005
Fault offset: 0x0045510d
Faulting process id: 0x20a0
Faulting application start time: 0x01d504a5b280527f
Faulting application path: C:\Users\I_SDU\source\Workspaces\MyApp\build\Debug\x86\MyApp.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
Report Id: a74cfc6e-451a-45be-b060-e9203f56d580
Faulting package full name:
Faulting package-relative application ID:
It is mostly C++/ MFC code, and surprisingly the Faulting module is clr.dll. Not sure what is going wrong.
Appreciate any inputs on how to resolve this crash issue.
TIA,
Jy
Continue reading...