HttpListener异步上下文泄漏
本文关键字:泄漏 上下文 异步 HttpListener | 更新日期: 2023-09-27 18:16:32
我有一个简单的HTTPServer实现,它使用System.Net.HttpListener。似乎我的AsyncCallbacks没有以某种方式处理,因此导致泄漏。
public abstract class HttpServer : IHttpServer, IDisposable
{
protected readonly HttpListener HttpListener = new HttpListener();
protected HttpServer(IEnumerable<string> prefixes)
{
WaitOnStartup = new AutoResetEvent(false);
foreach (var prefix in prefixes)
{
HttpListener.Prefixes.Add(prefix);
}
}
private void Process()
{
var result = HttpListener.BeginGetContext(ContextReceived, HttpListener);
result.AsyncWaitHandle.WaitOne(30000);
result.AsyncWaitHandle.Dispose();
}
protected abstract void ContextReceived(IAsyncResult ar);
[...]
}
public class MyHttpServer : HttpServer
{
public MyHttpServer(IEnumerable<string> prefixes) : base(prefixes) { }
protected override void ContextReceived(IAsyncResult ar)
{
var listener = ar.AsyncState as HttpListener;
if (listener == null) return;
var context = listener.EndGetContext(ar);
try
{
var request = context.Request;
var response = context.Response;
//handle the request...
}
finally
{
context.Response.Close();
listener.Close();
}
}
}
如果我运行内存分析器,它看起来像async句柄(BeginGetContext)不处置,这意味着AsyncCallback对象不断增加....
我错过了什么?
更新时间:下面是基类(HttpServer)的dispose ()
protected virtual void Dispose(bool disposing)
{
if (_disposed)
return;
if (disposing)
{
// Free any other managed objects here.
HttpListener.Stop();
HttpListener.Close();
WaitOnStartup.Dispose();
}
// Free any unmanaged objects here.
//
_disposed = true;
}
看起来我设法找到了问题,我不太确定为什么……
但是从@csharptest.net在多线程与。net HttpListener中发布的答案中获得灵感,我取代了使用:
private void Process()
{
var result = HttpListener.BeginGetContext(ContextReceived, HttpListener);
result.AsyncWaitHandle.WaitOne(30000);
result.AsyncWaitHandle.Dispose();
}
private void Process()
{
while (HttpListener.IsListening)
{
var result = HttpListener.BeginGetContext(ContextReceived, HttpListener);
if (WaitHandle.WaitAny(new[] { result.AsyncWaitHandle, _shutdown }) == 0)
return;
}
}