I just activated madExcept and let it do its thing. It happens on program exit. The program is not fully unloaded yet, the GUI is still visible and the program is cleaning up things.
When I forcefully trigger an exception while the program is running, I get a proper madExcept exception dialog with a stack trace and all the other options.
However, this "exit exception" wasn't captured by madExcept anymore.
I thought that maybe madExcept was already finalized during process shutdown, but if your GUI is still visible that seems unlikely.
Can you reproduce this problem on your development PC? If not, how often does this happen for users? Can they run tests for you? Or is it so rare that it's hard to test properly?
Hm, there is still something weird going on. Even when the program is running I get the standard exception dialog in many cases. What could be wrong? Anything I can check? We are using madExcept in another project and there it is working fine. But in this project something is wrong.
Does this always happen for any exception (even a manually raised test exception)? Or does it only happen sometimes? Can you reproduce the problem at all on your dev PC?