You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 18, 2018. It is now read-only.
I'm running the RTM bits and got the following stack trace after pressing CTRL+C on the dotnet run command line on Windows:
Unhandled Exception: System.ObjectDisposedException: The SafeHandle was closed.
at System.Runtime.InteropServices.SafeHandle.DangerousAddRef(Boolean& success)
at System.StubHelpers.StubHelpers.SafeHandleAddRef(SafeHandle pHandle, Boolean& success)
at Microsoft.AspNetCore.Server.Kestrel.Internal.Networking.Libuv.NativeMethods.uv_async_send(UvAsyncHandle handle)
at Microsoft.AspNetCore.Server.Kestrel.Internal.Networking.Libuv.async_send(UvAsyncHandle handle)
at Microsoft.AspNetCore.Server.Kestrel.Internal.KestrelThread.PostCloseHandle(Action`1 callback, IntPtr handle)
at Microsoft.AspNetCore.Server.Kestrel.Internal.Networking.UvHandle.ReleaseHandle()
at Microsoft.AspNetCore.Server.Kestrel.Internal.Networking.UvStreamHandle.ReleaseHandle()
at System.Runtime.InteropServices.SafeHandle.InternalFinalize()
at System.Runtime.InteropServices.SafeHandle.Finalize()
By that time, Kestrel had seen two requests on localhost: One for / that sent a context.Response.Redirect('/foo/') and the one for /foo/ that returned a 404.
I cannot reproduce this on subsequent runs.
The text was updated successfully, but these errors were encountered:
I think the problem is that Autofac as my DI container doesn't provide an IServiceProvider that implements IDisposable. That means the entire application stops by ways of the finalizer.
Isn't the IServiceProvider that's returned from ConfigureServices required to implement IDisposable?
I'm running the RTM bits and got the following stack trace after pressing CTRL+C on the
dotnet run
command line on Windows:By that time, Kestrel had seen two requests on localhost: One for
/
that sent acontext.Response.Redirect('/foo/')
and the one for/foo/
that returned a 404.I cannot reproduce this on subsequent runs.
The text was updated successfully, but these errors were encountered: