Potential HttpClient Ntlm memory leak RRS feed

  • Question

  • User40481 posted

    It looks like there is a memory leak in HttpClient when using Ntlm authentication. HttpClient seems to work ok if no credentials are used, but when request is authorized (server responds with 200 OK) memory starts to climb.

    Attached is a sample app, which makes a connection to the server we have set up (code for the server is also included). We will remove the server in a week, but wanted to make it easy to test for somebody willing to help.

    The app is a console app, few lines of code which just makes a connection and checks that response is 200 OK. If you let it run for a couple of minutes you should see memory rise.

    To try, open HttpClientMemoryLeak.zip in Xamarin studio and run (it will make a connection to a server we have set up). You can also run your own server.

    Are we missing something? Is there another way to use it? If this is a bug in mono, where do we post this? Is this the correct place?

    Friday, December 4, 2015 11:53 AM

All replies

  • User35201 posted

    That sounds like a mono bug. HttpClient is not a OS X specific API, so we get it from mono.

    I filed a mono bug here:


    with your example attached.

    Friday, December 4, 2015 1:46 PM