Use a threading.Lock when threads update a counter, and a synchronized multiprocessing.Value (with its lock held around the entire increment) when processes do. A bare counter += 1 is a read-modify-write sequence, so it can lose updates even when the counter is a shared multiprocessing value.
Choose the counter for your concurrency model
First identify whether the workers are threads in one process or independent processes. The memory model determines which counter and synchronization primitive are appropriate.
| Workers | Recommended counter | How to make an increment safe | Best fit |
|---|---|---|---|
| Threads | A normal integer plus one shared threading.Lock |
Hold the lock while reading, adding, and writing | Small state shared inside one process |
| Processes | multiprocessing.Value or multiprocessing.Array |
Use with counter.get_lock(): around the complete read-modify-write |
One scalar or a fixed-size set of values |
| Processes needing Python containers | multiprocessing.Manager proxies |
Use a manager-provided lock (or another process-safe lock) around compound updates | Shared dictionaries, lists, and other richer objects |
| Processes needing a custom memory layout | multiprocessing.shared_memory.SharedMemory |
Define the byte layout and provide synchronization yourself | Direct access to a named memory block |
Why counter += 1 can lose increments
An increment consists of three logical operations:
- Read the current value.
- Add one (or another increment) to the local value.
- Write the result back.
Two workers can read the same old value, calculate the same new value, and then overwrite each other. For example, if both read 10, both calculate 11, and both write 11, the counter advances once instead of twice.
The synchronization must cover the entire read-modify-write sequence. Protecting only the read or only the assignment does not make the operation atomic. Python’s multiprocessing documentation explicitly warns that operations such as += involving a read and a write are not atomic.
#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
Safely incrementing a counter from threads
Threads share the process’s memory, so they can update one ordinary integer. They still need a lock to define a critical section and prevent interleaving updates.
Basic thread example
import threading
counter = 0
counter_lock = threading.Lock()
def worker(increments: int) -> None:
global counter
for _ in range(increments):
with counter_lock:
counter += 1
threads = [threading.Thread(target=worker, args=(10_000,))
for _ in range(4)]
for thread in threads:
thread.start()
for thread in threads:
thread.join()
print(counter) # 40_000
The lock and the counter must be the same shared objects for every worker thread. If a worker creates its own lock, the workers are not coordinating and updates can still collide.
Keep the critical section narrow
Do work that does not touch the counter outside the with block. A short critical section reduces contention while preserving correctness:
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
for item in items:
result = process_item(item) # no counter access here
with counter_lock:
counter += 1
Do not rely on the CPython GIL as a counter-safety mechanism. Interpreter-lock behavior is not the documented contract for a compound update, and free-threaded Python builds make that assumption even less reliable. Use an explicit lock.
Recommended Free Tools
Safely incrementing a counter from processes with multiprocessing.Value
Processes have separate address spaces. A normal global integer is therefore private to each process. multiprocessing.Value creates a shared, synchronized scalar that processes can access.
Correct increment pattern
import multiprocessing as mp
def worker(counter, increments: int) -> None:
for _ in range(increments):
with counter.get_lock():
counter.value += 1
if __name__ == "__main__":
counter = mp.Value("i", 0)
processes = [mp.Process(target=worker, args=(counter, 10_000))
for _ in range(4)]
for process in processes:
process.start()
for process in processes:
process.join()
print(counter.value) # 40_000
Value supplies a synchronization lock by default. That lock protects individual access to value, but the increment still has two accesses, so acquire the lock explicitly around the whole expression with counter.get_lock().
Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
When a separate lock is useful
You can disable the automatically created lock and coordinate the value with a lock shared by several fields, but then every access must use that lock consistently:
counter = mp.Value("i", 0, lock=False)
counter_lock = mp.Lock()
# In every process:
with counter_lock:
counter.value += 1
A shared lock is especially useful when an update must keep multiple counters or a counter and another shared value consistent as one transaction.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallUsing multiprocessing.Array for several counters
Array is suitable for a fixed-size collection of shared numeric values. Like Value, it is synchronized by default, but a compound update still needs the associated lock.
Rank #4
- Dual Converters, Infinite Potential:Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
import multiprocessing as mp
def worker(counts, index: int, increments: int) -> None:
for _ in range(increments):
with counts.get_lock():
counts[index] += 1
if __name__ == "__main__":
counts = mp.Array("i", [0, 0, 0])
processes = [mp.Process(target=worker, args=(counts, i, 5_000))
for i in range(3)]
for process in processes:
process.start()
for process in processes:
process.join()
print(list(counts))
The array’s one lock serializes updates to all elements. If independent counters do not need a consistent combined snapshot, separate values and locks can allow more concurrency.
When a multiprocessing.Manager is the better fit
A manager runs a server process and gives workers proxy objects such as dictionaries, lists, locks, values, and arrays. It is convenient when the shared state is richer than one scalar or a fixed numeric array.
Manager-backed scalar with an explicit lock
import multiprocessing as mp
def worker(counter, counter_lock, increments: int) -> None:
for _ in range(increments):
with counter_lock:
counter.value += 1
if __name__ == "__main__":
with mp.Manager() as manager:
counter = manager.Value("i", 0)
counter_lock = manager.Lock()
processes = [mp.Process(target=worker,
args=(counter, counter_lock, 10_000))
for _ in range(4)]
for process in processes:
process.start()
for process in processes:
process.join()
print(counter.value)
The lock is explicit because the important guarantee is that the read and write happen under one process-safe critical section. Manager operations cross a server-process boundary, so they generally carry more overhead than direct synchronized shared memory. Choose a manager for flexibility, not for the lowest-latency counter.
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
Manager containers need the same rule
with manager.dict({"completed": 0}) as totals:
totals_lock = manager.Lock()
# In each worker:
with totals_lock:
totals["completed"] = totals["completed"] + 1
Proxy methods are separate calls. A sequence such as “get a value, add one, set the value” is still a compound operation and needs a lock.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Using multiprocessing.shared_memory for direct access
SharedMemory creates or attaches to a named block of bytes that multiple processes can access directly. It does not provide a counter abstraction or automatic atomic increments: your program must define the layout, encode and decode values, and synchronize updates.
Eight-byte counter with a process lock
import multiprocessing as mp
import struct
from multiprocessing import shared_memory
def worker(shm_name: str, counter_lock, increments: int) -> None:
shm = shared_memory.SharedMemory(name=shm_name)
try:
for _ in range(increments):
with counter_lock:
current = struct.unpack_from("q", shm.buf, 0)[0]
struct.pack_into("q", shm.buf, 0, current + 1)
finally:
shm.close()
if __name__ == "__main__":
shm = shared_memory.SharedMemory(create=True, size=8)
counter_lock = mp.Lock()
try:
struct.pack_into("q", shm.buf, 0, 0)
processes = [mp.Process(target=worker,
args=(shm.name, counter_lock, 10_000))
for _ in range(4)]
for process in processes:
process.start()
for process in processes:
process.join()
print(struct.unpack_from("q", shm.buf, 0)[0])
finally:
shm.close()
shm.unlink()
Every process closes its own handle with close(). The creator (or another single coordinator) calls unlink() once, after all users have finished, to remove the named block. If a process exits without cleanup, the block can remain until the platform’s shared-memory cleanup mechanisms reclaim it.
Shared memory is useful when you need a defined binary layout, large arrays, or direct access without proxy calls. It also increases your responsibility for alignment, data types, bounds, synchronization, and cleanup.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsCommon failure modes and fixes
- Using a normal global with processes: each process updates its own copy. Use
Value,Array, a manager proxy, or shared memory. - Writing
counter.value += 1without a lock: the individual property accesses may be synchronized, but the complete read-modify-write is not atomic. Holdcounter.get_lock(). - Locking only one worker: all workers that update the state must use the same lock object.
- Creating a lock inside each worker: those locks are unrelated. Create the lock before starting workers and pass or inherit it.
- Assuming a manager makes compound operations atomic: proxy calls are separate operations. Use a manager lock around the sequence.
- Forgetting to join processes: read the final value only after every worker has completed and been joined.
- Leaking shared memory: call
close()in each process andunlink()once after the final user is done. - Relying on start-method accidents: write worker functions at module scope and put process creation under
if __name__ == "__main__":, so the program also works with start methods that import the main module in a fresh interpreter.
A practical decision checklist
- If all workers are threads, use one ordinary counter and one
threading.Lock. - If workers are processes and the state is one numeric value, use
multiprocessing.Valueand holdget_lock()around each increment. - If the state is a fixed numeric collection, use
multiprocessing.Arraywith its lock, or design separate locks when independent updates can proceed independently. - If workers need dictionaries, lists, or other proxy-supported objects, use a
multiprocessing.Managerand protect multi-step updates with a shared lock. - If you need direct access to a custom byte layout, use
SharedMemory, add your own synchronization, and document ownership and cleanup. - Test with enough workers and increments to expose lost updates, then verify the final value only after all workers have joined.
Bottom line
Safe counter increments require synchronizing the read-modify-write operation, not merely choosing a container that is described as “shared.” Use an explicit thread lock for threads, Value or Array plus their lock for ordinary process-shared numbers, a manager for flexible proxy state, and shared memory only when you need direct, custom-managed storage.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

