Since #15233 has been merged, the lockdata becomes a static local variable with a well-defined initialization order:

Its destructor ~LockData() is called at program exit.

At the same time, "if a function-local ... static object was destroyed and then that function is called from the destructor..., the behavior is undefined."

It seems possible that at program exit the lockdata object is destroyed before a global RecursiveMutex destructor calls DeleteLock(), which in turn calls GetLockData() with UB.