nhorman
commented
3 weeks ago Based on discussion with Engineering, we have determined that it is infeasible to replace atexit currently with library destructors based on the various methods and orders in which library unloading occurs on various platforms. We have decided that, given this discovery, that atexit should be left in place currently, and an epic created for 3.5 to plan its removal by eliminating global variables, and requiring context initializtation for every use case, targeting a 4.0 release
We need to figure out how to remove atexit from our library to repair a number of common user issues