[Solved] Identify the problem in this Ruby code that uses threads: counter = 0 threads = 3.times.map do Thread.new do 100.times { counter += 1 } end end threads.each(&:join) puts counter | Ruby

Ruby - Concurrent Programming

Identify the problem in this Ruby code that uses threads:

counter = 0
threads = 3.times.map do
  Thread.new do
    100.times { counter += 1 }
  end
end
threads.each(&:join)
puts counter

AThread.new syntax is incorrect

BThreads are not joined, so program ends early

CNo Mutex used, so race condition may cause wrong counter value

DCounter variable is not initialized

Step-by-Step Solution

Solution:

Step 1: Check thread safety of counter increment
Multiple threads increment counter without synchronization, causing race conditions.
Step 2: Identify missing Mutex usage
Without Mutex, increments can overlap and produce incorrect final value.
Final Answer:
No Mutex used, so race condition may cause wrong counter value -> Option C
Quick Check:
Missing Mutex causes race condition [OK]

Quick Trick: Always use Mutex to protect shared variables [OK]

Common Mistakes:

Master "Concurrent Programming" in Ruby

9 interactive learning modes - each teaches the same concept differently

More Ruby Quizzes

Identify the problem in this Ruby code that uses threads: