Closed Cimplex closed 9 years ago
Thanks for the report. I've corrected the problem using an internal lock.
I do agree that the problem is weird. According to the usages it isn't obvious why it happens. But it's probably that both the read and send completion ports detect the disconnect and tries to clean up.
In HttpMessageEncoder.cs:Line 144, I've noticed it throwing a really really weird error.
_message.Body.Dispose( );
was throwing the error. Apparently_message
was null?!?! Even after yourif
statement... Threading is beyond me.I fixed it by locking the whole class, but I don't know if that is the best way to do it.
Either way, sweet project for sure! Thanks