Job objects
Grouping processes with shared limits, UI restrictions, and teardown rules.
Related labs
Hands-on exercises for this area — in the browser or on a Windows machine.
Process tree explorer
Walk a sample parent/child tree from System to Explorer and a user app.
Open labOfficial Microsoft docs
Closest official references related to this topic on Microsoft Learn.
Why it matters
Jobs are how Windows implements 'kill whole tree', sandbox-style limits, and some browser/app isolation patterns.
Mental model
A job object is a container. Processes assigned to it share quotas and can be terminated together.
How it works
- 1A parent creates a job and assigns child processes to it.
- 2Limits can cap memory, UI access, or breakaway behavior depending on configuration.
- 3Destroying or closing a job can terminate all processes still inside it.
Key terms
- Job object
- A kernel object that groups processes under shared policy.
- Breakaway
- Whether a child process may escape the job.
Closing a console kills the whole build tree
Build tools often run under a job so Ctrl+C or closing the console tears down compiler children together.
Common misconception
Jobs are not the same as process trees. Parent/child hierarchy and job membership are separate relationships.
You should read next
Ranked from your current topic, related links, branch depth, and any active guided path.
intermediate
Kernel objects
Handles, object manager, names, and reference counting basics.
Related topic
intermediate
Access tokens
SIDs, privileges, impersonation, and the identity payload every process carries.
Related topic
beginner
Services & background infrastructure
How Windows launches, groups, isolates, and supervises long-running background components.
Related topic