Doom crash after 2.5 years of real-world runtime confirmed on real hardware
11 comments
·September 16, 2025serf
The easy way to e-Nostradamus predictions:
"See this crash?
I predicted it years ago.
Don't ask me how, I couldn't tell you."
p.s. I had an old iPaq that I wouldn't have trusted to run for longer than a day and stay stable, kudos for that at the very minimum.
sunrunner
Not a comment on the post, but I sure wish Jira would load even half as quickly as this site.
antsar
It takes serious hardware investment [0] to pull that off.
JoshGlazebrook
2038 is going to be a fun year.
0cf8612b2e1e
I am going to need to see this replicated before I can believe.
ranger_danger
Seems to be a PocketPC port of Doom, with no source given or even a snippet of the relevant code/variable name/etc. shown at all.
null
unixhero
Yes. I think it it seems like it was the os that overflowed, and not Doom in this case.
nomel
It's also running on very old hardware, potentially with some electrolytic capacitors that have dried up. And, there's always the possibility that it's a gamma ray [1]!
[1] https://www.bbc.com/future/article/20221011-how-space-weathe...
null
About a year ago I was looking at Crash Bandicoot timer systems and I found that Crash 3 has a constantly incrementing int32. It only resets if you die.
Left for 2.26 years, it will overflow.
When it does finally overflow, we get "minus" time and the game breaks in funny ways. I did a video about it: https://youtu.be/f7ZzoyVLu58