My code makes synchronous HttpWebRequest and HttpRebResponse calls. In VS
2003, I am getting memory leaks and event handle leaks. I am closing all
streams and using "using"statemen ts. I have used .Net memory profiler from
Sci Tech to analyze the leaks and they are coming from inside HttpWebRequest
and HttpRebResponse . When I run my code on VS2005, I do not get any leaks.
Is this problem fixed in .Net 1.1 SP1? I may not be able to wait for VS
2005.
Steve Binney
See this blog for a detailed description of the problem:
http://dturini.blogspot.com/2004/06/...with-some.html
Damn! Handle leaks on the CLR!
On the past few days, I'm dealing with some hard to find resource leaks. We
seem to be pushing some areas CLR to their limit. You may say, "hey, how can
you get resource leaks in a garbage collected environment"?.
Well, the simple code below will leak lots of handles.
private void MakeARequest() { HttpWebRequest wr =
(HttpWebRequest )WebRequest.Cre ate("http://www.microsoft.c om/");
wr.Proxy = WebProxy.GetDef aultProxy(); wr.Proxy.Creden tials =
CredentialCache .DefaultCredent ials; using (HttpWebRespons e wrp =
(HttpWebRespons e)wr.GetRespons e()) { using (Stream
s = wrp.GetResponse Stream()) { using
(StreamReader sr = new StreamReader(s) )
{ string st = sr.ReadToEnd();
sr.Close();
s.Close(); } } } }
Did you see it? It isn't missing a single Close() or Dispose() call, and yet
leaks lots of handles. The biggest the page, the more handles it leaks.
I've been using an evaluation version (10 days remaining...) of the great
SciTech's .NET memory profiler and noticed that the CLR is forgetting to
dispose some (a lot!) ManualResetEven t, Sockets, and some internal Streams
and Readers.
After a while, I found that the culprit are the synchronous HttpWeb(Request ,
Response) methods, and, by calling the assynchronous versions, I was able to
reduce it a lot. Even the returned stream, System.Net.Conn ectStream have
these problems.
The only problem is when the request throws an Exception, it still leaks
lots of handles, and, by now, it seems that I can do nothing about it...
Steve Binney
