error on reading from skt : -1, errno 10053

[HelloTodayWolrd]

The libwebsockets version is 4.3.0, the connection method is ws://127.0.0.1, 30 frames are sent per second, 300~500k per frame, after refreshing the web page several times to reconnect to the server, it cannot be connected, LWS_CALLBACK_SERVER_WRITEABLE cannot be triggered, and the screen is refreshed crazily with errors, "2025-06-17 18:42:45.990
"2025-06-17 18:42:46.015 WebSocketServer log:info:[2025/06/17 18:42:46:0150] I: [wsisrv|9|adopted]: lws_ssl_capable_read_no_ssl: error on reading from skt : -1, errno 10053\n\n"
"2025-06-17 18:42:46.015 WebSocketServer log:info:[2025/06/17 18:42:46:0150] I: rops_handle_POLLIN_ws: LWS_SSL_CAPABLE_ERROR\n\n"
"2025-06-17 18:42:46.015 WebSocketServer log:info:[2025/06/17 18:42:46:0150] I: [wsisrv|9|adopted]: __lws_close_free_wsi: caller: close_and_handled\n\n"
"2025-06-17 18:42:46.015 WebSocketServer log:info:[2025/06/17 18:42:46:0150] I: [wsisrv|9|adopted]: __lws_close_free_wsi: LRS_FLUSHING_BEFORE_CLOSE\n\n"
"2025-06-17 18:42:46.015 WebSocketServer log:info:[2025/06/17 18:42:46:0150] I: [wsisrv|9|adopted]: lws_ssl_capable_read_no_ssl: error on reading from skt : -1, errno 10053\n\n"
"2025-06-17 18:42:46.015 WebSocketServer log:info:[2025/06/17 18:42:46:0150] I: rops_handle_POLLIN_ws: LWS_SSL_CAPABLE_ERROR\n\n"

[lws-team]

Dunno, but...

• 4.3.0 isn't a great choice. It's from 2021, since then there are a lot of improvements that can be found on v4.3-stable branch

• main branch has a lot of additional improvements over v4.3

• trying to send 15MB/s to your web browser is pretty optimistic

• rather than show logs for it after it's dead, it's more interesting to see logs for when it fails to come back the first time after refreshing.

• Your server code shouldn't have any thread using lws apis other than the thread that created the context

[HelloTodayWolrd]

Dunno, but...

• 4.3.0 isn't a great choice. It's from 2021, since then there are a lot of improvements that can be found on v4.3-stable branch
• main branch has a lot of additional improvements over v4.3
• trying to send 15MB/s to your web browser is pretty optimistic
• rather than show logs for it after it's dead, it's more interesting to see logs for when it fails to come back the first time after refreshing.
• Your server code shouldn't have any thread using lws apis other than the thread that created the context

First of all, thank you very much for your reply.
What I am doing is transmitting local screenshots to the client. To ensure the image quality is clear and the frame rate is between 20 and 30, the amount of data sent is relatively large.
I think the cause of the problem should be that when sending a large amount of data frequently to the client, the client suddenly disconnects, causing the server to try to read the client data interface "errno 10053" error, and this error did not allow the server to interrupt the reading operation, thus outputting a large number of "errno 10053" errors.
I will update libwebsockets to the latest version in two days to see if the problem can be solved. If not, I may want to consider whether the problem can be solved by modifying the libwebsocket source code.

[lws-team]

You're very welcome to propose fixes for lws, if that's what's needed.

10053 is winsock for WSAECONNABORTED, it seems to be related to the peer not accepting data any more. It might not be directly related since you can expect this to happen when the browser closes its current tab session due to the refresh.