Operating Systems - Starvation vs Deadlock vs Livelock - Differences & Examples
In a multi-threaded system, which scenario best describes when starvation occurs?
In a multi-threaded system, which scenario best describes when starvation occurs?
easy🔍 Pattern Recognition Q11 of Q15
Step-by-Step Solution
Step 1: Identify starvation characteristics
Starvation happens when a process is perpetually denied access to resources due to scheduling policies favoring others, typically higher-priority processes.Step 2: Analyze each option
A low-priority process never gets CPU time because higher-priority processes keep running correctly describes starvation as a low-priority process being indefinitely postponed. Two or more processes wait indefinitely for each other to release resources describes deadlock, where processes wait on each other. Processes continuously change states without making progress due to resource contention describes livelock, where processes are active but not progressing. A process is blocked waiting for I/O to complete is normal blocking, not starvation.Final Answer:
Option B -> Option BQuick Check:
Starvation involves indefinite postponement due to priority, matching a low-priority process never getting CPU time because higher-priority processes keep running.
Quick Trick: Starvation = low priority starved of CPU time
Common Mistakes:
MISTAKES- Confusing starvation with deadlock
- Thinking livelock is the same as starvation
Trap Explanation:
PITFALL- Options B and C are plausible because they involve waiting and resource issues, but they represent starvation and livelock respectively, not deadlock.
Interviewer Note:
CONTEXT- Tests candidate's ability to distinguish starvation from other resource contention problems.
Master "Starvation vs Deadlock vs Livelock - Differences & Examples" in Operating Systems
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Operating Systems Quizzes