According to the output from Valgrind, it is in ENGINE_new (in
/usr/lib/libcrypto.so.0.9.8). Is there any cleaning of libcrypto
initializations that is done in the curl cleanup functions? It looks
that as a libcurl developer you will have the same issue if you try to
fix it. It appears that you won't be able to access this ENGINE
pointer and thus the ENGINE_free won't fit as a solution. Instead we
would need a generic libcrypto or openssh cleanup function that frees
this ENGINE.

- Huzaifa

On Mon, Jan 5, 2009 at 10:57 PM, Daniel Stenberg <daniel_at_haxx.se> wrote:
> On Mon, 5 Jan 2009, Huzaifa Al Nahas wrote:
>
>> After more research, it appears that it is a bug in libcurl design. I
>> contacted openssl support team and they replied suggesting that the memory
>> leak can be avoided by using ENGINE_free. However, this function takes as
>> argument a pointer to the ENGINE that was called in ENGINE_new. AFAIK
>> libcurl does not give the library user access to this pointer. What do you
>> think?
>
> What engine pointer that libcurl allocates are you saying it should call
> ENGINE_free() on?
>
> --
>
> / daniel.haxx.se
>
Received on 2009-01-06