What was the Apollo 11 Guidance Computer bug?

A resource lock leak in LGYRO during gyro caging. Two missing instructions in BADEND path. Hangs all future alignments silently.

How was the Apollo Guidance Computer bug found after 57 years?

JUXT used Allium to spec 130k lines of assembly. Tracked resource lifecycles across all paths. Flagged the unpaired release.

Could the Apollo 11 bug have stranded the astronauts?

Yes—Michael Collins' solo alignments would've hung. No comms behind Moon. Looked like hardware fail. No fix.

🧠 Engineering Culture

Apollo 11's Guidance Computer Hid a Kill-Switch Bug for 57 Years

Everyone figured the Apollo Guidance Computer was bulletproof—reviewed by thousands, emulated endlessly. Then, 57 years later, a tiny bug surfaces that could've left Michael Collins stranded in orbit.

theAIcatchup Apr 07, 2026 3 min read

Apollo 11 Guidance Computer core rope memory with highlighted buggy code snippet

⚡ Key Takeaways

Even the most reviewed code—like Apollo's—hides resource leaks in error paths. 𝕏
Restarts and defensive coding can mask bugs, not fix them. 𝕏
Formal specs (like Allium) catch what reviews miss; modern langs help, but manual resources don't. 𝕏

Published by

theAIcatchup

Ship faster. Build smarter.

#Apollo Guidance Computer #formal verification #resource leak #resource leaks #software bugs

Worth sharing?

Get the best Developer Tools stories of the week in your inbox — no noise, no spam.

Originally reported by dev.to

⚡ Key Takeaways

The 60-Second TL;DR

theAIcatchup

Share this article

Worth sharing?

Related Stories

Tech Recruiters Trash Your Resume in 6 Seconds Flat—I've Seen It for 20 Years

7300 Product Jobs Open in 2026: Recovery or Elite-Only Club?

Artemis II's Upside-Down Earth: 54 Years After Apollo, Still Breathless

Slack's Async Edge Crushes Teams for Dev Teams in 2026

Stay in the loop