What is a Process?
What you'll learn: You'll discover what a process is and how it differs from a program sitting on your disk.
The Static vs Dynamic Distinction
When you write code and save it as a file (say, calculator.exe or game.py), that's a program—a static collection of instructions stored on disk. It's like a recipe in a cookbook: just sitting there, doing nothing.
A process is what happens when you actually run that program. It's the program in execution—alive, active, and using the computer's resources. Think of it as a chef actively following the recipe: ingredients in hand, stove on, work in progress.
What Makes a Process?
When the operating system loads a program from disk into memory and starts executing it, the program becomes a process. A process includes:
- The program's instructions loaded into memory
- Data the program is working with (variables, buffers)
- Execution state: which instruction is running, register values, program counter
- System resources: open files, network connections, allocated memory
You can run the same program multiple times simultaneously, creating multiple independent processes. For example, opening three browser windows creates three separate processes from one browser program—each with its own memory, state, and data.
Why the Distinction Matters
The OS manages processes, not programs. It schedules which process gets CPU time, protects each process's memory from others, and cleans up resources when a process finishes. A program is passive; a process is the active, managed unit of work.
Key Takeaway: A process is a program in execution—the dynamic, running instance that consumes memory and CPU time, while a program is the static code stored on disk.