We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug nng_socket_close may hang on window in some situations, from the call stack, it is waiting for pipe close.
nng/src/core/socket.c
Line 691 in dba356d
Expected behavior It should return normally
Actual Behavior Hang
To Reproduce Possible reproduce senario: Create IPC/pair socket, but don't send any data for a period large than 5 seconds, and then close the socket.
** Environment Details **
Additional context from my debugging, there is a issue in IOCP worker, timeout error does not handle correctly, which cause it exit unexpected.
nng/src/platform/windows/win_io.c
Line 42 in dba356d
Potential Fix has attached
winio.patch
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
nng_socket_close may hang on window in some situations, from the call stack, it is waiting for pipe close.
nng/src/core/socket.c
Line 691 in dba356d
Expected behavior
It should return normally
Actual Behavior
Hang
To Reproduce
Possible reproduce senario:
Create IPC/pair socket, but don't send any data for a period large than 5 seconds, and then close the socket.
** Environment Details **
Additional context
from my debugging, there is a issue in IOCP worker, timeout error does not handle correctly, which cause it exit unexpected.
nng/src/platform/windows/win_io.c
Line 42 in dba356d
Potential Fix has attached
winio.patch
The text was updated successfully, but these errors were encountered: