Server Eventually Gets "Stuck"

[bendangelo]

I been running some tests and realized after hitting an endpoint continously like 100 times or so. The server will not respond and the client will keep waiting (using a ruby client, this might matter). The endpoint doesn't need to do anything special, just return an empty response.

I haven't dug into it, but I suspect a pack sent to the server gets "missed" at some point and this causes the whole thing to stall.

One thing I also noticed was a fiber never gets deleted once opened but that's a separate issue.

[jgaskins]

Hmm, I haven't noticed this since I fixed #11. Do you have some code to reproduce this?