• Use logging to narrow down which part of code the program is executing when it crashes. Keep adding log until you narrow it down enough to see the issue.
• Enable debug information in the release build (both compiler and linker); many variables won t show up correctly, but it should at least give you sensible backtrace (unless the freeze is due to stack smashing or stack overflow), which is usually enough if you keep functions short and doing just one thing.
• Memory leaks can t cause freezes. Other forms of memory misuse are however quite likely to. In my experience overrunning a buffer often cause freezes when that buffer is freed as the free function follows the corrupted block chains. Also watch for any other kind of Undefined Behaviour. There is a lot of it in C/C++ and it usually behaves as you expect in debug and completely randomly when optimized.
• Try building and running the program under DUMA library to check for buffer overruns. Be warned though that:
  • It requires a lot of memory. I mean easily like thousand times more. So you can only test on simple cases.
  • Microsoft headers tend to abuse their internal allocation functions and mismatch e.g. regular malloc and internal __debug_free (or the other way round). So might get a few cases that you ll have to carefully workaround by including those system headers into the duma one before it redefines the functions.
• Try building the program for Linux and run it under Valgrind. That will check more problems in addition to buffer overruns and won t use that much memory (only twice as normal, but it is slower, approximately 20 times).

调试版本通常初始化所有分配的内存( MSVC 以调试配置以 < code> 0xCD 填充它们 ) 。 也许您在班级中有一些未初始化的值, 包括 GCC 配置和 MSVC 调试配置, 它得到了一个“ 幸运” 值, 但是在 MSVC 发布时它没有 。

这里是"https://stackoverflow.com/a/127404/737620" MSVC 使用的其他神奇数字。

因此寻找未初始化的变量、属性和分配的内存区块。

Thank you all, especially Cody Gray and MikMik, I found it! As some of you recommended I told VS to generate debug information and disabled optimizations in the release configuration. Then I started the program and paused it. Alternatively I remotely attached to the running process. This helped me finding the region where the error was. The reasons were infinite loops, caused by reads behind the boundaries of an array and a missing exclusion of an invalid case. Both led to unreachable stopping conditions at runtime. The esoteric part came from the fact, that my program uses some randomized values. That s life...