Ticking Timebomb in Mac OS

Nobody will ever need more than 2^32 milliseconds of uptime - Steve Jobs

The Lineagen

When I saw 49 days, it took me back to a similar bug in Windows 95. Any system running Windows 95 would suddenly hang after running for 49 days because of a similar issue; a 32-bit uptime clock would wrap around and cause problems. It went undiscovered for a some years since keeping Windows 95 running for that long without crashing was something of a miracle.

If a bug disappears when I put a log statement... You bet I'll solve it with a sleep(100). and make it a next month's problem when the whole backend collapses from a workload that magically takes 120ms instead of the 20ms it used to

Getting hot and sweaty eating mom's spaghetti. Update: Lines were as straight as uncooked spaghetti

Came for the explanations. Stuck around for the stunning lines

You always struck me as someone who’s great at ‘doing lines’

I once had a Bug that disappeared with a Console log, not entirely because of timing, but because logging pulled the calculation onto the main thread, where it worked. Multithreading is one hell of a drug.

I thought I was INSANE when my macbook's networking just stops working after being on for too long! Holy vindication

KERNEL builds crazy fast, open source infra for AI agents to access the internet. Trusted by Framer, Cash App, and 3000+ teams https://trm.sh/kernel