Running parallel benchmarks using `&` chaining does not exit correctly on Linux

Description

$ autocannon -d 20 -c 100 http://localhost:3000/a & autocannon -d 20 -c 100 http://localhost:3000/b & autocannon -d 20 -c 100 http://localhost:3000/c

Contributor guide

Tech stack

nodejsshell

Domain

cliperformance

Issue type

bug

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

2

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-3 hours

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

fresh

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

clear

Prerequisites

Node.js basicsUnderstanding of process signals

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

70

Research direction

Investigate how autocannon handles SIGINT and process groups. Look at the main entry point and child process spawning. The issue mentions that ghost processes remain; ensure that when the parent process exits, all spawned benchmarks are properly terminated. Possibly need to use `process.on('exit')` or `process.on('SIGINT')` to kill child processes.