Closed Rumpel78 closed 6 years ago
What's the version you have this issue?
I am using latest NuGet Version in production and tried the latest github version for testing.
Essentially I have stripped away all code, tried to pinpoint my error and now I think this happens somewhere in the StringEncoder/Decoder, or, perhaps, this is not really an error.
@Rumpel78 I think I found the root cause of the false positive leak report.
@StormHub Looks good, no more messages - thanks!
I have following pipeline:
DummyHandler:
I always get following message after ~2000-3000 connections:
If I remove the WriteAndFlushAsync call, this message does not appear. I suspected the channel being closed before the ouput could be written, so I have tried calling WriteAndFlushAsync with await, Task.WaitAll and WriteAndFlushAsync("").Wait() but the result is always the same.
I am trying to implement an IP-Block - a handler testing the connected IP and closing the channel with an error message. I would like to avoid a memory leak.
Any ideas on this?