From: Richard Levitte <levitte@openssl.org>
Date: Wed, 23 Mar 2005 21:13:35 +0000 (+0000)
Subject: Change the memory leak FAQ entry to describe the levels of thread safety in each... 
X-Git-Tag: OpenSSL_0_9_7g~23
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=2950db59955852483206cd5ebb3d89a49f0ffc5f;p=openssl

Change the memory leak FAQ entry to describe the levels of thread safety in each function
---

diff --git a/FAQ b/FAQ
index 99f5c27779..eb40ca1677 100644
--- a/FAQ
+++ b/FAQ
@@ -792,9 +792,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().
 
 
 ===============================================================================