提交 6141b86a 编写于 作者: R Richard Levitte

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

上级 23fadaa0
...@@ -793,9 +793,20 @@ that is allocated when an application starts up. Since such tables do not grow ...@@ -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().
=============================================================================== ===============================================================================
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册