On Thu Jul 25 09:11:23 2024 +0000, Piotr Caban wrote:
Again, the implementation of `_ctime64_s` is broken (it shouldn't use non thread-safe `_localtime64` function) but there's no leak. Value returned by `_localtime64` should not be freed.
I've created !6155 that addresses _ctime*_s functions not being thread-safe bug.