Benoit Chesneau
Benoit Chesneau
well the issue is that a message is still on the process heap after cloising the socket. I have a fix for it. Will take care of it later today....
can you try #482?
can anyone provides me a link on which I can reproduce the issue?
@stephenmoloney do you mean the link? I need to reporduce it apart of the another lib ...
@critch thanks. Quite possible indeed. I think that rather than pausing i should rather receive actively at some point. I will have a closer looks, thanks for the reproducible way.
fixed in latest master.
@rozap you mean 2 consecutive call without receiving the message? can you show a simple snippet for it? just fyi right after the next release i will revisit the stream...
@billgloff how does it happen? Can you open a ticket with more details if you can?
@binarylogic do you have a simple way to reproduce it? maybe a simple snippet showing how the async request is handled is enough
Thanks! This patch doesn't handle empty line which however. The main difference with #537 is using a buffer of 8192 where #537 is using a buffer of 4096, I wonder...