On the ABI compatibility of std::future

[PiliLatiesa]

The following program:

#include <future>
#include <iostream>

void Fn() {}

int main()
{
  std::future<void> Future;
  
  Future = std::async(std::launch::async, Fn);
  
  Future.get();
  
  std::cin.get();
  
  return 0;
}

compiled with:

cl Source.cpp /EHsc /O2 /MD
Compilador de optimización de C/C++ de Microsoft (R) versión 19.42.34436 para x86
(C) Microsoft Corporation. Todos los derechos reservados.

Source.cpp
Microsoft (R) Incremental Linker Version 14.42.34436.0
Copyright (C) Microsoft Corporation.  All rights reserved.

/out:Source.exe
Source.obj

crashes when executed on a computer with the MSVC redistributable version 14.29.30135 installed.

Isn't this combination supposed to work?

[YexuanXiao]

You should ensure that the runtime version is at least the STL header files version.

[StephanTLavavej]

Yexuan Xiao (@YexuanXiao) is correct. You're probably encountering the mutex change that shipped in VS 2022 17.10. As https://github.com/microsoft/STL/wiki/Changelog#vs-2022-1710 explains:

• Fixed bugs:
  • Fixed mutex's constructor to be constexpr. #3824 #4000 #4339
    • Note: Programs that aren't following the documented restrictions on binary compatibility may encounter null dereferences in mutex machinery. You must follow this rule:

      When you mix binaries built by different supported versions of the toolset, the Redistributable version must be at least as new as the latest toolset used by any app component.

    • You can define _DISABLE_CONSTEXPR_MUTEX_CONSTRUCTOR as an escape hatch.