The Overloaded Mini

Why the Mac mini slowed to a crawl, in plain English — what was actually running, what we cleared, and what will bring it back if we leave it.

17 September 2026 · measured on the mini · cleanup partly done

The mini was doing 208 things at once. Four of them were real. Everything else had finished hours ago and was still sitting there, holding memory and watching files.

1 — Too many helpers

Every piece of work opens a helper session. When the work ends, the helper doesn't leave. It keeps its memory, and it keeps watching your files for changes.

What was runningCount
Helper sessions open208
Doing anything at all4
Background programs590
Memory held by them32 GB

2 — Too many copies

Each piece of work also makes its own copy of the project. There were 304. Every copy carries tens of thousands of small files, and the Mac watches all of them continuously.

3 — The cleaner says it's fine

A cleanup runs every morning and reports a green tick. Here is what it actually did today:

checked 17 never looked at 191 removed 0 — still reported green

4 — One file jams the rest

The cleaner won't touch a copy that has unsaved work in it, which is sensible. But 13 copies count as "unsaved work" because of a single file that rewrites itself — package-lock.json. Nobody edited it; the computer did.

5 — What we cleared

Before

208 helpers
304 copies
40% memory free

After

7 helpers
100 copies
86% memory free

Jammed programs went from 42 down to 1. Nothing was lost: every helper that was closed can be reopened with everything it remembered.

6 — What isn't finished

The one-line version

Nothing was broken. The mini was buried under finished work that nothing was clearing away, and the thing meant to clear it has been reporting success while doing almost nothing.

PropFlow Docs