Skip to content
This repository was archived by the owner on Dec 18, 2018. It is now read-only.

Stress: leaking Microsoft.AspNet.Server.Kestrel.Http.SocketOutput+ThisWriteReq as they are rooted by strong handles #19

Closed
KKhurin opened this issue Jul 9, 2014 · 2 comments
Closed

Stress: leaking Microsoft.AspNet.Server.Kestrel.Http.SocketOutput+ThisWriteReq as they are rooted by strong handles #19

KKhurin opened this issue Jul 9, 2014 · 2 comments
Labels
3 - Done bug
Milestone
1.0.0-alpha3

Comments

@KKhurin
Copy link

KKhurin commented Jul 9, 2014

No description provided.

@KKhurin
Copy link
Author

KKhurin commented Jul 9, 2014

This exception causes the handle to not get closed:
(16f4.cd0): CLR exception - code e0434352 (first chance)
KestrelThread.DoPostWork System.Exception:
Error -4077 ECONNRESET connection reset by peer
at Microsoft.AspNet.Server.Kestrel.Networking.Libuv.Check
at Microsoft.AspNet.Server.Kestrel.Networking.Libuv.write
at Microsoft.AspNet.Server.Kestrel.Networking.UvWriteReq.Write
at Microsoft.AspNet.Server.Kestrel.Http.SocketOutput.ThisWriteReq.Write()
at Microsoft.AspNet.Server.Kestrel.Http.SocketOutput.b__0(Object x)
at Microsoft.AspNet.Server.Kestrel.KestrelThread.DoPostWork()

@KKhurin
Copy link
Author

KKhurin commented Jul 9, 2014

Similar leak could happen with the disconnect on Read

lodejard pushed a commit that referenced this issue Jul 9, 2014
@loudej
Guarding against leaking GCHandles in read/write operations
de6c32d 
See #19
@lodejard lodejard added this to the 0.1-alpha3 milestone Jul 9, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
3 - Done bug
Projects
None yet
Milestone
1.0.0-alpha3
Development

No branches or pull requests
3 participants
@davidfowl @lodejard @KKhurin