Note that because these locale objects are declared 'static', they don't go out of scope until the library is unloaded. So the only way this results in a memory leak is if a process is opening libssl via dlopen, then unloading it, then loading it again.
Note that because these locale objects are declared 'static', they don't go out of scope until the library is unloaded. So the only way this results in a memory leak is if a process is opening libssl via dlopen, then unloading it, then loading it again.