Zombie Process
Version 1.0.0 · Updated 2026-07-30
CORE DEFINITION
A child process has finished running, but the parent process has not yet read its exit status, causing it to still occupy a slot in the process table. It does not consume resources but occupies a slot. Scaffolding role: Unfinished past. Those relationships or projects that have ended but have not been psychologically "archived" are zombie processes. Although they are no longer active, they occupy your psychological bandwidth. You must perform an explicit "reap" to formally say goodbye and release space.
SCAFFOLDING EFFECT
Reduce cognitive load
Unfinished past. Those relationships or projects that have ended but have not been psychologically "archived" are zombie processes. Although they are no longer active, they occupy your psychological bandwidth. You must perform an explicit "reap" to formally say goodbye and release space.
Anchor fast decisions
A child process ends but remains in the process table, waiting for the parent to call wait() to read its exit status; if the parent delays reaping, it exists in a "zombie state"—not consuming CPU or memory, but occupying a process ID (PID). The mechanism is that an "unfinished exit" occupies a resource slot.
MINIMUM ACTION
In progress 0/4Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- zh.wikipedia.orghttps://zh.wikipedia.org/wiki/%E5%83%B5%E5%B0%B8%E8%BF%9B%E7%A8%8Bverified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS