The way 'deadlocks' cause a computer system to freeze

Computers love a bit of unnecessary faff, and the 'deadlock' is the ultimate digital sulk. It’s like two people meeting on a narrow garden path, both too stubborn to step aside.

Imagine I’m holding the teapot but need the tea leaves, while you’re clutching the leaves but won't budge until I hand over the pot. We both just stand there, frozen, while the water goes cold.

In your system, two programs each hold a resource the other needs. They’re stuck in a circular 'after you' that never ends, leaving your screen completely paralyzed.

Wait, why can't the computer just force one to let go?

In a perfect world, the system would just snatch the teapot away. But some resources are 'non-preemptible,' which is a fancy way of saying they are too fragile to be interrupted.

Imagine if I yanked a half-knitted jumper off your needles just because someone else needed the wool. You would end up with a tangled mess of dropped stitches and ruined work.

If the system forcibly kills a task mid-process, it risks corrupting your data or leaving 'digital crumbs' everywhere. It is often safer to let the system freeze than to let it break your files.

So it just stays stuck until I hit the reset button?

Exactly. A deadlock is a permanent stalemate. Left to its own devices, the computer would happily sit there until the sun burns out, waiting for a resource that’s never coming. It is a lot of faff for absolutely no result.

Some clever systems have a 'watchdog'—think of it as a grumpy lifeguard at the beach. If it notices no one has moved a muscle for a while, it blows the whistle and forces a restart to clear the pool.

But usually, it is down to you. You are the one who has to march over, flip the switch, and tell those digital toddlers to start their chores all over again from the beginning.

How does that lifeguard actually know if we're stuck or just thinking very hard?

It’s all about the 'heartbeat.' Imagine I’m the lifeguard and I ask you to wave every ten seconds while you’re out in the surf. If you stop waving, I’m diving in to stop the faff.

The watchdog is just a timer. The software must give it a digital nudge at regular intervals to prove it’s still active. If the timer hits zero, the lifeguard assumes you've frozen and blows the whistle.

It’s a blunt tool. It doesn't 'know' you're stuck; it just loses patience. If a task is just being slow, the watchdog might restart the system anyway.

But isn't it a nightmare if it restarts while I'm still working?

It’s a right old mess when it gets it wrong. It’s like a pushy waiter whisking away your Sunday roast just because you paused for a sip of water.

This is the "Great Faff" of engineering: setting the timeout. If the timer is too twitchy, the computer restarts for no reason. If it’s too relaxed, you’re left staring at a frozen screen for ages.

There’s no perfect setting. It’s just a grumpy compromise to keep the whole system from staying paralyzed forever.