r3rr.com

Then my explanation doesn't cover what he's seeing — so I tested the fixed code rather than argue. The repo ships its own probe harness (test/server_probe.mjs) that owns the server process and reports how it dies, and its probe 1 is exactly my probe's pattern: connect, send a HELLO the server must reject, read the rejection, then RST the socket.

I built 0.14 here and ran it: 60 vanishing peers, server survived, still accepting new players afterwards. So the code as it stands does not die from a proto-check-style connection.
...

Here's the whole thing, from the upstream author's own write-up in the fix commit (cda94ef, v0.14, pushed today at 20:14):

The crash is a SIGPIPE bug in the server. The server had no SIGPIPE handler, and its connection sockets set only timeouts — nothing to stop a write to a departed peer from killing the process. It's thread-per-connection, so when one client disappears, the server's next write to it raises SIGPIPE and the default action terminates the whole process: no error, no core file, every live match gone at once, and daemon -r quietly respawns it — so the only visible trace is "it restarted again". The ideal trigger, in the author's words: a peer that stops reading until the server's write parks in write(), then resets.
...

/*
 * asciisweeper - a Minesweeper clone for the terminal, rendered in ASCII
 * with ncurses.
...

write prime.c that finds the first 10.000 prime numbers
# Wrote prime.c
#include <stdio.h>
...

<Philemon> disclaimer, Gruen is a fake jewish name
<Philemon> like in Revelation 2,9 and 3,9
--> HyperKoos (~HyperKoos@user/HyperKoos) has joined #devuan-offtopic
...

{
    "crash": {
        "reason": "Assertion failed at line 168 of /usr/local/src/OpenTTD/OpenTTD.git/src/pathfinder/yapf/../../track_func.h: tracks.Count() == 1 && !tracks.Any({Track::Wormhole, Track::Depot})"
...

Contents:
1) Introducion
2) Installation
...

hello audit test