New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

Fixed it need 18mins timeout to shutdown socket when it lost network … #1091

Open

G-MoYang wants to merge 1 commit into zaphoyd:master from G-MoYang:bugs/XueZhi_for_fixing_disconnecting_issue

G-MoYang commented Mar 8, 2023

…connection


          Fixed it need 18mins timeout to shutdown socket when it lost network …

946847e

…connection

Author

G-MoYang commented Mar 8, 2023

I am using SignalR library.
websocketpp is one port of vcpkg.
Envoriment: Raspberry pi， Raspbian GNU/Linux 11
Reprso Steps:

Setup connection with server by SignalR(websocket)
Disable network connection.
Call close() in ws_client_wspp.cpp
It send close frame to server.
It timeout by 10s close hanshake.
It not cancel socket successfully, so it keep wait. (handle_close_handshake_timeout()->terminate()->transport_con_type::async_shutdown()->handle_async_shutdown_timeout()->cancel_socket_checked()->socket_con_type::cancel_socket())

G-MoYang mentioned this pull request

It will need about 18 mins to stop connection(disconnecting to disconnected) when it lost network(Like disble WiFi insterface). And it wil cause Linux Segmentation Fault when I try to call hub_connection::stop() while connection state is disconnecting. dotnet/aspnetcore#46801

Closed

1 task

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet