It has never occurred in the debugger, only in regular games. And the debugger runs at about 5% speed of the regular .exe version.
Debugger runs at 5% is good enough, I've seen worse.
But if it never happens, that's a problem yes.. It's like your car never starting, but every time the mechanic comes looking, it turns on and spins as a kitty .. I hate such bugs. But like I said, there are systems that are simply defined to hit such bugs.. simply rebuild those systems and have the debugger running day and night on them.. with 5% that might take you 2 weeks still, but some systems simply hit even random bugs so often that they're not random anymore.
Some people simply have bad luck having those systems.. usually it means something is going wrong with pointers or mallocs.. you can compile your whole program once with a catch for those.. although debugging that might slow down even further :(
or, compile dll's and other files with the debug info and hand those to your beta testers, and ask for specific beta testers that can debug and program. Might help catching random bugs..
But yes I must admit, even then, you might simply have bad luck and those bugs never appear when you need them to..
btw, I only had this save bug when I played a "non-legal" version... because I couldn't buy it.. after 3 days trying many internet shops I finally was able to buy it legally, since then it didn't crash anymore..
So, might be cracked, might be not, but the cracked version does seem to increase the chance to hit this bug.
So you might wanna try it that way (if people report it still exists)