Closed
Description
I suspect there is a memory leak, dangling pointer, or uninitialized variable somewhere. It can't be reliably reproduced (and could be a compiler bug) but if I run
ctest --repeat-until-fail 7 --schedule-random -j 12
on a macOS MBP with 6 physical cores & 12 logical cores I can usually get test 10 to segfault. Probably should throw valgrind at it on a linux box.