segmentation fault when using "flip" or "rotate"

[stephanecharette]

In release builds, when using the "flip" or "rotate" functionality on a dataset that contains very large images, DarkMark may segfault. Stack trace looks like this:

2021-10-21 09:10:35 aborting due to signal: "Segmentation fault" [signal #11]
2021-10-21 09:10:35 aborting due to signal: "Segmentation fault" [signal #11]
2021-10-21 09:10:35 backtrace #0: ./DarkMark: get_backtrace[abi:cxx11]() +0x57 [0x55ec0d199ec7]
2021-10-21 09:10:35 backtrace #1: ./DarkMark: dm::DarkMarkApplication::signal_handler(int) +0x18b [0x55ec0d19afdb]
2021-10-21 09:10:35 backtrace #2: /lib/x86_64-linux-gnu/libc.so.6(+0x46210) [0x7f504be5e210]
2021-10-21 09:10:35 backtrace #3: /lib/x86_64-linux-gnu/libopencv_imgproc.so.4.2(+0x27113c) [0x7f504c97913c]
2021-10-21 09:10:35 backtrace #4: /lib/x86_64-linux-gnu/libopencv_core.so.4.2(+0x2110e8) [0x7f504c5690e8]
2021-10-21 09:10:35 backtrace #5: /lib/x86_64-linux-gnu/libtbb.so.2(+0x2c545) [0x7f504809c545]
2021-10-21 09:10:35 backtrace #6: /lib/x86_64-linux-gnu/libtbb.so.2(+0x2c80f) [0x7f504809c80f]
2021-10-21 09:10:35 backtrace #7: /lib/x86_64-linux-gnu/libtbb.so.2(+0x25bd7) [0x7f5048095bd7]
2021-10-21 09:10:35 backtrace #8: /lib/x86_64-linux-gnu/libtbb.so.2(+0x24498) [0x7f5048094498]
2021-10-21 09:10:35 backtrace #9: /lib/x86_64-linux-gnu/libtbb.so.2(+0x20880) [0x7f5048090880]
2021-10-21 09:10:35 backtrace #10: /lib/x86_64-linux-gnu/libtbb.so.2(+0x20a8d) [0x7f5048090a8d]
2021-10-21 09:10:35 backtrace #11: /lib/x86_64-linux-gnu/libpthread.so.0(+0x9609) [0x7f504d0bb609]
2021-10-21 09:10:35 backtrace #12: /lib/x86_64-linux-gnu/libc.so.6: clone +0x43 [0x7f504bf3a293]
fish: “./DarkMark” terminated by signal SIGABRT (Abort)

Note that this does not happen when you set the build type to "Debug". It only seems to happen with "Release" and "RelWithDebInfo".