Hi Christian,
Am 20.09.2011 11:13, schrieb Christian Hägele:
> after upgrading libCurl in our application from 7.21.2 to 7.22.0 we encountered
> the following problem:
> Our server-application does lots of outgoing http-connections to different hosts
> via the multi-interface. We used to compile libcul with the USE_WINDOWS_SSPI
> macro (we used that for NTLM-proxy-authentication on the client side). It seems
> that some of the NTLM changes in libCurl triggered a serious memory leak in
> the windows-service lsass.exe.
> After rebuilding libCurl without the USE_WINDOWS_SSPI macro, as we don't need
> NTLM on the server side, the problem went away.
>
> Has anybody else saw that problem? Is this a problem on libcurl or in windows
> (I suppose it's a windows problem triggered by something in libcurl).
does this mean that even though you dont use SSPI just the fact that it
is compiled-in triggers already the leak?
Also if its not too big a burdon can you please check if 7.21.7 has that
leak or not? This way we can perhaps rule out any changes from .2 to .7 ...

Gün.

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2011-09-20