Python Why Shared Mutable State Can Cause Race Conditions

Race conditions happen when an outcome depends on uncontrolled timing between operations on shared mutable state.

Understanding the Concept

Race conditions happen when an outcome depends on uncontrolled timing between operations on shared mutable state. Protect multi-step changes with locks or redesign to exchange messages.

Use local variables or immutable messages when sharing state is unnecessary.

How to reason about concurrent execution

Workers may start and finish in a different order on every run. Focus on ownership of data, how work and errors move between workers, and what happens when one worker stops early. Locks protect invariants, queues exchange messages, and explicit shutdown logic prevents blocked or orphaned workers.

Concurrency adds overhead and failure modes. Begin with a working sequential solution, choose bounded worker counts and explicit timeouts, then measure whether overlap or parallel execution improves the target workload.

Worked Example

Read the code from the first line to the last. Identify which values are inputs, which operation is being demonstrated and what should happen before running it.

from threading import Lock
counter = 0
lock = Lock()
def increment():
    global counter
    with lock:
        counter += 1
increment()
increment()
print(counter)

Walkthrough: What Each Part Does

• The imports make threading available. These are standard-library building blocks unless the example explicitly names an external tool.
• The definition increment creates reusable behavior. Its body runs when called, awaited or instantiated; defining it alone does not run the body of an ordinary function.
• The with or async with scope controls lifetime. Setup takes place on entry, and cleanup runs on exit even when an exception interrupts the body.
• The last lines coordinate completion and inspect results. Actual worker scheduling may differ between executions.

This demonstration focuses on one practical behavior. Before changing several lines, vary one input or one configuration choice and check whether the result changes for the reason you expected.

Example Output

2

The output above was captured by running the example in the available Python environment. The order of concurrent events, durations and platform-dependent values can legitimately differ on your computer.

Important Behavior and Edge Cases

Assuming a short statement or the presence of the GIL makes every sequence of reads and writes atomic.

Use local variables or immutable messages when sharing state is unnecessary.

Practice Exercise

Remove the lock in a threaded stress test and compare behavior, without relying on a failure in every run.

Write down the result you expect before running your changed code. Check at least one normal case and one boundary or failure case. If your example starts workers or opens resources, verify how they are cleaned up.

Further reading: official documentation and API reference.

Common Beginner Mistakes

• Assuming a short statement or the presence of the GIL makes every sequence of reads and writes atomic.
• Forgetting to handle worker errors and shutdown, even when the normal completion path appears correct.

Key Takeaways

• Race conditions happen when an outcome depends on uncontrolled timing between operations on shared mutable state.
• Use local variables or immutable messages when sharing state is unnecessary.
• Practice: Remove the lock in a threaded stress test and compare behavior, without relying on a failure in every run.