R12.6: Worker thread termination

Short answer: Spawn worker instances call terminate() upon task completion. A worker that is never terminated keeps a thread and its memory.

Group: Memory and resource leaks. Status: stable. Generated from the rule definitions; do not edit by hand.

Playground: https://brevio.pro/tools/agent-guard-playground?rule=R12.6

What it catches

Worker thread termination: spawn worker instances call terminate() upon task completion.

Why

A worker that is never terminated keeps a thread and its memory.

A bad example

const w = new Worker(file);

A good example

const w = new Worker(file);
w.on('message', done).on('message', () => w.terminate());

How it is checked

Nothing yet. No scanner and no slice card checks it: it is a standing rule for authors and reviewers.

How to silence it

A person can silence one finding with brevio-core: ignore R12.6 -- reason on the line or the line above. Without the reason it does not count. An agent cannot silence it: the agent hook and the MCP tools never honour the comment, and a pull request that adds one is reported until a reviewer allows it. Fixing the code is still the better answer.

To change what the rule flags, edit its definition in dev_rules.py or code_rules/__init__.py. That is a code change and is reviewed like one.

R12.7 Temp file deterministic deletion
R12.8 No unbounded collection growth
R12.1 Event listener teardown
R12.2 Timer lifecycle cleanup
Every rule