A few years ago I designed a way to detect bit-flips in Firefox crash reports and last year we deployed an actual memory tester that runs on user machines after the browser crashes. Today I was looking at the data that comes out of these tests and now I'm 100% positive that the heuristic is sound and a lot of the crashes we see are from users with bad memory or similarly flaky hardware. Here's a few numbers to give you an idea of how large the problem is. 🧵 1/5

I connected to Xcode's MCP server (xcrun mcpbridge), and requested a list of all the tools. Then I threw that at Claude and had it whip up a "cheat sheet". In case you're curious what the agents have at their disposal.