|Summary:||Potential HttpClient Ntlm memory leak|
|Product:||[Mono] Class Libraries||Reporter:||Chris Hamons <chris.hamons>|
|Component:||System.Net.Http||Assignee:||Marek Safar <masafa>|
|Tags:||Is this bug a regression?:||---|
|Last known good build:|
Repro part 1
Repro part 2
Real repro part 2
Description Chris Hamons 2015-12-04 13:44:19 UTC
Created attachment 14121 [details] Repro part 1 From https://forums.xamarin.com/discussion/57141/potential-httpclient-ntlm-memory-leak 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.
Comment 3 Chris Hamons 2015-12-04 13:46:07 UTC
Repro web server requires asp.net, which I do not have access to a windows dev box to validate.
Comment 4 Marek Safar 2015-12-07 17:02:02 UTC
Fixed in master