Subject: Re: [libssh2] #298: Memory leak

Re: [libssh2] #298: Memory leak

From: libssh2 Trac <trac_at_libssh2.stuge.se>
Date: Thu, 02 Apr 2015 16:06:35 -0000

#298: Memory leak
----------------------+--------------------
  Reporter: double | Owner:
      Type: defect | Status: closed
  Priority: normal | Milestone: 1.4.3
 Component: crypto | Version: 1.5.0
Resolution: wontfix | Keywords:
Blocked By: | Blocks:
----------------------+--------------------
Changes (by alamaison):

 * status: new => closed
 * resolution: => wontfix

Comment:

 Agreed. OpenSSL doesn't count calls to OpenSSL_add_all_algorithms() and
 matching calls to EVP_cleanup(). Until
 [http://rt.openssl.org/Ticket/Display.html?id=2217&user=guest&pass=guest
 that is fixed] (don't hold your breath), we can't safely call
 EVP_cleanup().

 If you want to avoid the memory leak (it's not really a leak - just looks
 like one to valgrind), call it yourself in your application. 

-- 
Ticket URL: <https://trac.libssh2.org/ticket/298#comment:2>
libssh2 <https://trac.libssh2.org/>
C library for writing portable SSH2 clients
_______________________________________________
libssh2-devel http://cool.haxx.se/cgi-bin/mailman/listinfo/libssh2-devel
Received on 2015-04-02