Processes and Multitasking

Open the task manager on your computer — Activity Monitor on a Mac, Task Manager on Windows — and you'll see a long list of things running. Dozens of them. Most you never started and have never heard of, yet they're all alive right now.

Each entry in that list is a process — one program the operating system is currently running. In the previous chapter you saw what "running a program" means: its instructions get loaded from storage into memory, and the CPU works through them. A process is exactly that program, mid-run. The operating system's job is to keep all of these going at once, which is the subject of this topic.

One CPUone at a time

→

Process Aa brief turn

→

Process Bthen a turn

→

Process Cand so on

What Is a Process?

A process is a single running program. The same app can even be running as more than one process at a time — open three browser windows and the system may track them as separate processes — but the idea holds: a process is a program in the middle of doing its work, occupying memory and taking turns on the CPU.

This is the difference between a program at rest and a program in motion. The app sitting on your storage, not yet opened, is just files — a recipe in a cookbook. The moment you launch it, the operating system creates a process for it, and that process is the recipe actually being cooked. Close the app and the process ends; the files on storage stay exactly where they were.

How Can So Many Run at Once?

Here is the part that surprises people. A simple processor core can really only do one thing at any single instant — it follows one instruction, then the next. So how can your computer play music, download a file, and show this page seemingly all at the same time?

The trick is speed. The operating system gives the CPU to one process for a tiny slice of time — a few thousandths of a second — then pauses it, hands the CPU to the next process for its slice, and keeps cycling through them. It switches so fast that, to you, every process looks like it never stopped. This rapid taking-of-turns is what multitasking actually is.

A chef in a small kitchen works the same way. Only one pan gets full attention at a time, but the chef stirs one, turns to chop for the next, checks the oven, and circles back — switching constantly. No single dish is ever truly cooked "at the same time" as another, yet by moving fast enough, the whole meal comes together. The CPU is the chef; each process is a dish; the operating system decides whose turn is next.

One honest note: this is the simple picture. Real computers also have several CPU cores, so a handful of processes genuinely do run at the very same instant, and the operating system blends true parallel work with the fast-switching just described. The take-turns idea is the foundation; the multiple-cores detail sits on top of it.

Background and Foreground

Most of the processes in that task-manager list are running in the background — doing their work without any window on screen. Your system checks for updates, syncs files to the cloud, watches for incoming messages, and keeps the clock right, all through background processes you never see.

A foreground process is the one you're actively looking at and using — the app whose window is in front of you. The split is just about attention, not importance. A background process is every bit as real and running as the foreground one; it simply has no window asking for your focus.

When a Process Misbehaves

Sometimes a process gets stuck — caught in a loop, or waiting forever for something that never comes. You've seen the result: a window greys out and the system labels it "not responding." The process is still there, still a process, but it has stopped taking its turns usefully.

Because the operating system is the one handing out turns on the CPU, it also holds the power to stop any process entirely. When you "force quit" a frozen app, you're asking the operating system to end that process by hand. The app vanishes from memory; your saved files on storage are untouched, and you can simply launch it again, which starts a fresh process.