[openssl-commits] [web] master update

[Rich Salz]

The branch master has been updated
       via  9c52c88fe28320b881917cc14a69335fd599943b (commit)
      from  3ad8a7f02eac3be90857ba96fd5337eb3e10734e (commit)


- Log -----------------------------------------------------------------
commit 9c52c88fe28320b881917cc14a69335fd599943b
Author: Rich Salz <rsalz at akamai.com>
Date:   Thu Jul 6 07:54:58 2017 -0400

    Auto-cleanup for 1.1.0

-----------------------------------------------------------------------

Summary of changes:
 docs/faq-3-prog.txt | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/docs/faq-3-prog.txt b/docs/faq-3-prog.txt
index 5c2324c..45a33ad 100644
--- a/docs/faq-3-prog.txt
+++ b/docs/faq-3-prog.txt
@@ -207,7 +207,10 @@ In most cases the cause of an apparent memory leak is an OpenSSL internal table
 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
+Starting with OpenSSL 1.1.0, everything should be cleaned up on exit (or
+when the shared library unloads).  If not, please find out what resource is
+leaked and report an issue.  In previous releases, internal tables can be
+freed up when an application closes using various
 functions.  Currently these include following:
 
 Thread-local cleanup functions include ERR_remove_state(3).