metallermartin

This happens to me as well. I suspect the reason is that in Visual Studio under Test->Test Settings->Default architecture an incorrect architecture is selected. E.g. you build x64, but look...

Well, obviously the Test Settings are not the reason for this message. I again got it today with the correct setting

We have customer reports of crashes showing the same stack trace. However, we use [mimalloc](https://github.com/microsoft/mimalloc) as a custom allocator instead of oneTBBs. So the issue does not seem specific to...