On FreeBSD and MacOSX libcrypto library we believe destructor calls reference memory which was allocated by a dynamically loaded engine (possibly also providers) which were unloaded prior to destructors for libcryptos are run. this causes an invalid memory reference and a crash.
This investigation is meant to confirm the above is what is going on on those platforms, and if it turns out to be the case we need to re-evaluate how we handle memory cleanup at exit
On FreeBSD and MacOSX libcrypto library we believe destructor calls reference memory which was allocated by a dynamically loaded engine (possibly also providers) which were unloaded prior to destructors for libcryptos are run. this causes an invalid memory reference and a crash.
This investigation is meant to confirm the above is what is going on on those platforms, and if it turns out to be the case we need to re-evaluate how we handle memory cleanup at exit
report fidings to OTC on tuesday
openssl/openssl#24148