Clients suddenly stop receiving messages

Open
#600 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
networking

Research direction

Start by reproducing the high-FPS server-to-client message flow and inspect the client receive path alongside the Wireshark TCP Window Full and ZeroWindow observations. Determine whether the issue exposes a configurable receive-buffer or read-flushing control, and document a clear reproduction and resolution.

Written by the indexing model from the issue text.

Description

I am sending messages from server to client with rather high FPS (trying to understand limit) but after just few hundreds of them client suddenly stops receiving them.

Debug with Wireshark shows that one of packets gets: TCP Window Full and client can send packets, but they come with TCP ZeroWindow.

So this looks like client is not able to read from socket fast enough. Is there any control over receiving buffer or a way to flush it on each read message?

Thanks in advance.

Dominant language
C#
Stars
6.1k
Forks
1.7k
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sta/websocket-sharp

All issues in sta/websocket-sharp

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.