The Runtime Theory

How Processes, Threads, and the Cost of Sharing works

An interactive concept flow for processes, threads, and the cost of sharing, from its assumptions through the main operation and boundary checks.

The Runtime Theory Team05 stages

trace / request.md

CONTRACTREPRESENTATIONOPERATIONBOUNDARYRESULT

readyA process is a protected resource container with an address space and operating-system-managed resources. A thread is an execution stream with its own program counter, registers, and stack. Threads in one process normally share code and heap memory, which makes communication cheap but coordination necessary.

Use the stages in order to explain processes, threads, and the cost of sharing. Each stage makes one assumption visible: what the operation promises, what representation it uses, how state changes, which boundary can invalidate a shortcut, and what evidence confirms the result.

For a worked explanation, continue to the topic article and execution trace.

Not started

Sign in to save your learning progress.

Sign in to save