std::chrono::current_zone crashes on MSVC builds

The simple program in https://godbolt.org/z/Gs35jzodK that compiles:

#include <chrono>

int main() {
  (void)std::chrono::current_zone();
}

crashes on MSVC builds with error : Program returned: 3221226505 (this is STATUS_STACK_BUFFER_OVERRUN)

[StephanTLavavej]

https://github.com/microsoft/STL/wiki/VS-2019-Changelog#vs-2019-1610

While the STL generally provides all features on all supported versions of Windows, leap seconds and time zones (which change over time) require OS support that was added to Windows 10. Specifically, updating the leap second database requires Windows 10 version 1809 or later, and time zones require icu.dll which is provided by Windows 10 version 1903/19H1 or later. This applies to both client and server OSes; note that Windows Server 2019 is based on Windows 10 version 1809.

If the VMs are using Windows Server 2019, that would explain this - it’s too old for time zones. Windows Server 2022 will work (that’s what the STL’s own test VMs use).

[timmy-ms]

We are currently blocked by the version of Windows that Kubernetes supports. As soon as we can upgrade to Server 2022 we will. Until then there is nothing we can do here sadly. 😦