What causes a lock-ordering deadlock between two mutexes?

When one thread locks A then B while another locks B then A, each can hold one lock and wait forever for the other, producing a classic deadlock.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix a Lock-Ordering Deadlock Between Two Mutexes

Quick answer: Establish a single global order in which all locks must be acquired and have every thread take them in that order, or use try-lock with backoff to avoid holding while blocked.

Two subsystems each guard their state with a mutex. Under load the game freezes: thread one holds the player lock and waits on the world lock, while thread two holds the world lock and waits on the player lock. Here is how to break the cycle.

How to fix it

1. Define one canonical lock order

Pick a fixed order for all locks (for example by address or an assigned rank) and require every code path to acquire them in that order, eliminating the cycle that causes deadlock.

2. Lock both at once when possible

If you must hold both, acquire them together with a primitive that locks multiple mutexes deadlock-free (such as C++ std::scoped_lock(a, b)).

3. Use try-lock with backoff

Where ordering is impractical, try to acquire the second lock and, on failure, release the first and retry, so no thread holds one lock while blocked on another.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

Reproduce it once with full context and the fix writes itself. The hunt is the expensive part.