Happy new year!!
We have one customer who has run into the following problem often. It is not reproducible, but there can be days where it does not ocurr at all, on other days it happen a couple of times or even more than 10 times.
What is happening is that our app is crashing but no exception is being logged - so we are kind of clueless as to what the cause of the problem could be.
We have been using madExcept for several months now and this is so far the only case where this is happening. One of my colleagues did a postmortem debug session with WinDbg after such a crash occurred on the customers machine and looking at the callstack it seems that there madExcept did intercept the exception but ended up in an endless loop?
Here is a screenshot of the callstack
This is a screenshot of the windows event viewer
Here is a link to the WinDbg dump file if it be of any use to you.https://www.dropbox.com/s/6qbbb0wesvmhymt/madExcept_dump100120171500.dmp?dl=0
Please let us know if there is anything useful/helpful you can gain from this.
Have you had similar cases in the past, where an unhandeled exception occurs but is somehow not logged?