Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Server does not stop sending, when client crashes.

Open
#9 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
Mostly clear
Activity status
Stale
Tech stack
cpp
Domain
networking

Research direction

Start by reproducing the issue with the reported ctsTraffic.exe UDP listener command. Trace the server's UDP receive and shutdown handling, including CTRL+C behavior. Done means the server stops after the client crashes or an appropriate timeout, and can be terminated reliably with CTRL+C.

Written by the indexing model from the issue text.

Description

Using UDP as protocol; when the client crashes, the server does not stop automatically (not even after a specific amount of time/packages).
It is also not possible to kill the execution with CTRL+c sometimes.

The server has been started with ctsTraffic.exe -listen:* -protocol:udp -bitspersecond:10000000000 -framerate:870000 -bufferdepth:1 -streamlength:60 -consoleverbosity:1

Dominant language
C++
Stars
289
Forks
54
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 microsoft/ctsTraffic

All issues in microsoft/ctsTraffic

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.