I can tell it’s some 32-bit millisecond counter without even opening the article. 49 days period is too specific.
And since I did not hear anything about MacOS network stack catastrophically breaking on any servers, the impact should be small.
49 days period is too specific.
49.7 days is also the maximum uptime for Windows 95 and 98.
No it’s not. That’s just the point at which a timer overflows which could cause a problem but it doesn’t guarantee one.
The article describes how they immediately went to look for an unsigned 32-bit millisecond counter when they noticed it was happening around 50 days since last reboot, because they already knew that association you describe.
Interesting writeup. Fun little story about the detective work involved.
AI generated crap. Lots of people posting in /r/Apple that they’ve uptimes many times longer than this without any issue.
I’ve encountered this before, on a Mac Pro 5,1. Same thing used to happen to my old Linux machine and I’ve seen it happen to Win2k waaaaaay back in the day. I recall the whole up-too-long-cant-network thing being quite common at one point. This article feels like a nothing burger.
Lol. Glad to see others using the term “nothing burger”.
As I explained elsewhere it’s just that. Hype for a new AI model that can’t understand the big picture nor the final details and is finding non-existent bugs.
It’s a great phrase for things like this lol
Yeah I haven’t seen my Mac Pro 6,1 do this in the 2y it’s been living in my rack running boinc jobs. Nor my M1 mini at work that goes untouched for months at a time bc I don’t need to go there.
These kinds of bugs have been around for ages. There was one like this in WinNT, and this was found when the OS was finally stable enough to run for as long as that…
That this bug was found just now tells me that nobody lets a Mac run for serious lengths of time…
Multiple reports on Apple’s community forums and open-source projects describe symptoms that match this bug precisely:
- Apple Community #250867747: macOS Catalina — “New TCP connections can not establish.” New connections enter SYN_SENT then immediately close. Existing connections unaffected. Only a reboot fixes it.
- Apple Community #252991075: “Mac Pro TCP/IP stops working.” TCP completely fails, but ping (ICMP) works normally.
- Podman issue #12495: “podman machine network connectivity stalls after some uptime” on macOS 12. The VM running on macOS shows outbound TCP failure with ICMP still functional, occurring after running for multiple weeks.
Amazing that nobody so far noticed the similarities to the WinNT bug of old.
It seems to me like nobody bothered to measure how long it took to trigger, and those in the first two threads seem unaware that it is caused by uptime and not some other random thing
Didn’t windows XP have a similar bug? Related to the windows uptime counter, iirc.
Windows 9x would crash after 49.7 days.
Windows Vista had a bug where the network stack would crash after 497 days, but if you didn’t care about networking the rest of the OS would continue to run.
Just reading this gave me a flashback to the old Windows 9x issue where, if you left a machine running “too long”, it would crash. 😅
Can’t recall the number of days, though. 38? 68? 78? Something like that.
That’s not a thing.
At 49.7 days a timer overflows. That could cause problems… It doesn’t guarantee problems.
That’s the one. And fair enough.
Had a couple of users tell me it crashed their PCs, but that was my only reference.
Man, the headline.
