Zombie process

On <a href="/facts/Unix/0pNL2seI">Unix</a> and <a href="/facts/Unix-like/YAKrAxzd">Unix-like</a> computer <a href="/facts/Operating_system/8XTuvMh2">operating systems</a>, a zombie process or defunct process is a <a href="/facts/Process_(computing)/Vcq7EnUV">process</a> that has completed execution (via the <a href="/facts/Exit_(system_call)/dnhClTUU">exit</a> <a href="/facts/System_call/NW44AFJr">system call</a>) but still has an entry in the <a href="/facts/Process_table/Vcq7EnUV">process table</a>: it is a process in the "<a href="/facts/Process_state/l8ghjY3V">terminated state</a>". This occurs for the <a href="/facts/Child_process/qwBcoGAq">child processes</a>, where the entry is still needed to allow the <a href="/facts/Parent_process/SGkeTvEu">parent process</a> to read its child's <a href="/facts/Exit_status/V3uTvuNo">exit status</a>: once the exit status is read via the <a href="/facts/Wait_(system_call)/pDCYnnyj">wait</a> <a href="/facts/System_call/NW44AFJr">system call</a>, the zombie's entry is removed from the process table and it is said to be "reaped". A child process initially becomes a zombie, only then being removed from the resource table. Under normal system operation, zombies are immediately waited on by their parent and then reaped by the system. Processes that stay zombies for a long time are usually an error and can cause a <a href="/facts/Resource_leak/6zxNKPXA">resource leak</a>. Generally, the only kernel resource they occupy is the process table entry, their process ID. However, zombies can also hold buffers open, consuming memory. Zombies can hold handles to file descriptors, which prevents the space for those files from being available to the filesystem. This effect can be seen by a difference between <a href="/facts/Du_(Unix)/ckVT5ceF">du</a> and <a href="/facts/Df_(Unix)/XYWlcgm9">df</a>. While du may show a large amount of free disk space, df will show a full partition. If the zombies are not cleaned, this can fill the root partition and crash the system.
The term zombie process derives from the common definition of <a href="/facts/Zombie/LR5MoBP8">zombie</a> — an <a href="/facts/Undead/Gcj3IwQ5">undead</a> person. In the term's metaphor, the child process has "died" but has not yet been "<a href="/facts/Personifications_of_death/sjp81fjl">reaped</a>". Unlike normal processes, the <a href="/facts/Kill_(command)/PjqmLTUR">kill</a> command has no effect on a zombie process.
Zombie processes should not be confused with <a href="/facts/Orphan_process/7fodYdF5">orphan processes</a>, a process that is still executing, but whose parent has died. When the parent dies, the orphaned child process is adopted by <a href="/facts/Init/0NuCuc1g">init</a>. When orphan processes die, they do not remain as zombie processes; instead, they are waited on by init.

Zombie process open-in-new

Zombie process