generic-library/openssl
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

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

Browse Source
This commit is contained in:
Richard Levitte 2005-03-23 21:14:59 +00:00
parent 23fadaa084
commit 6141b86a49
1 changed files with 14 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
FAQ
View File

@ -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. in size over time they are harmless.
These internal tables can be freed up when an application closes using various These internal tables can be freed up when an application closes using various
functions. Currently these include: EVP_cleanup(), ERR_remove_state(), functions. Currently these include following:
ERR_free_strings(), ENGINE_cleanup(), CONF_modules_unload() and
CRYPTO_cleanup_all_ex_data(). 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().
=============================================================================== ===============================================================================