Hello Everybody,
We have a unexpected, unpredictible crash that happens on our application only in rare circonstances; Especially on virtual servers in a Citrix environment but we also had the crash on different 64 bits Windows 7 computers.
THe crash is a native Windows low level crash, it is not a .net exception there it can't be caught in a try cath nor produces us an usable stracktrace we could investigate.
It is extremly complex to reproduce the bug, therefore trying to catch and debug the process win Visual in C++ Native mode is impossible.
The error message in french unfortunately, attached to this post states :
APPCRASH
IN the module StackHash_3e4b
Our Google investigations pinpointed a potential crash at loading a bad 32 bits dll in a 64 bits environment. But we have no clues. The app works fine on hundred of computers/citrix servers in the différents hospitals throughout france that use it.
The two native dependencies we think that could be guilty are :
1) WPF -> If the failure comes from a bad driver for instance (
2) Native Oracle dlls we are using for our datalayer and that we attack with the ORM Devart
Do you think it could come then from the dotConnect and its dependencies on Win32/64 Oracle native dlls ?
Thank you
Unexpected native crash in WPF 4.5 .Net application
Re: Unexpected native crash in WPF 4.5 .Net application
1. Please run Windows Event Viewer in this way: Start > Control Panel > System and Security> Administrative Tools > Event Viewer. Does it contain details about APPCRASHes you have encountered?
2. Try our recommendations listed at http://forums.devart.com/viewtopic.php? ... 271#p92379: latest (8.4.352) build, another Oracle client, etc. Notify us about the result.
2. Try our recommendations listed at http://forums.devart.com/viewtopic.php? ... 271#p92379: latest (8.4.352) build, another Oracle client, etc. Notify us about the result.
Re: Unexpected native crash in WPF 4.5 .Net application
Thank you for your response.
1) The appCrash doesn't contain a lot basically just the information we have in our post. I will copy the full content in the next post.
2) Thanks we are going to test this and notify the results.
Best Regards
1) The appCrash doesn't contain a lot basically just the information we have in our post. I will copy the full content in the next post.
2) Thanks we are going to test this and notify the results.
Best Regards