From 6141b86a49e5470556a912ca984b86ecd70d44f1 Mon Sep 17 00:00:00 2001 From: Richard Levitte Date: Wed, 23 Mar 2005 21:14:59 +0000 Subject: [PATCH 1/1] Change the memory leak FAQ entry to describe the levels of thread safety in each function --- FAQ | 17 ++++++++++++++--- 1 file changed, 14 insertions(+), 3 deletions(-) diff --git a/FAQ b/FAQ index a691db767f..dab94a0359 100644 --- a/FAQ +++ b/FAQ @@ -793,9 +793,20 @@ that is allocated when an application starts up. Since such tables do not grow in size over time they are harmless. These internal tables can be freed up when an application closes using various -functions. Currently these include: EVP_cleanup(), ERR_remove_state(), -ERR_free_strings(), ENGINE_cleanup(), CONF_modules_unload() and -CRYPTO_cleanup_all_ex_data(). +functions. Currently these include following: + +Thread-local cleanup functions: + + ERR_remove_state() + +Application-global cleanup functions that are aware of usage (and therefore +thread-safe): + + ENGINE_cleanup() and CONF_modules_unload() + +"Brutal" (thread-unsafe) Application-global cleanup functions: + + ERR_free_strings(), EVP_cleanup() and CRYPTO_cleanup_all_ex_data(). =============================================================================== -- 2.34.1