OpenSSLInitializer::uninitialize() not calling OSSL_PROVIDER_unload for OpenSSL v3 leaving memory leak #4385
Unanswered
yezenyounan
asked this question in
Q&A
Replies: 1 comment
-
|
No, we tried calling |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm using
Poco v1.12.4andOpenSSL v3.0.7throughvcpkg v2023.01.09, building on Ubuntu.In my application I call
Poco::Net::initializeSSL()in a class constructor andPoco::Net::uninitializeSSL()in the class's destructor.Poco::Net::initializeSSL()andPoco::Net::uninitializeSSL()callOpenSSLInitializer::initialize()andOpenSSLInitializer::uninitialize(), respectively.The
initialize()function callsOSSL_PROVIDER_loadfor OpenSSL v3, but theuninitialize()function does NOT callOSSL_PROVIDER_unloadfor OpenSSL v3.This causes my application to have memory leaks.
Is there a work around?
Beta Was this translation helpful? Give feedback.
All reactions