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.

vk6flab@lemmy.radio · 48 pts · 130d (10 replies)

So, why is this being disclosed here and not a CVE reported to Apple?

While contemplating that, my Mac has been up for longer than that and it's working fine.

The Mac I had before that was up for years, also fine.

So .. what is this really about?

mushroommunk@lemmy.today · 35 pts · 130d (1 reply)

A lot of these new AI found bugs are proving to be nothing burgers. Just a waste of money to try and hype the latest models.

They're either in old code not actually used anymore or miss a system interaction that fixes the supposed bug or just straight up are wrong.

LLMs are shit

homes@piefed.world · 9 pts · 130d

Yeah, macOS, like most UNIX/BSD and Linux systems (even NT systems), use BSD‘s rather ancient TCP/IP stack. And, like most systems, have found their own unique ways around whatever bugs once existed (or still exist) in that stack.

This case uses iMessage as an example, and it would be kind of foolish not to think that between the TCP/IP stack and macOS‘s internal messaging system there isn’t some kind of time reset handler before it gets handed off to iMessage.

hersh@literature.cafe · 11 pts · 130d (1 reply)

I've also had Macs online for years without issue.

I guess it only applies to "ephemeral" ports 49152–65535, though I'm not sure what range macOS actually uses. Wikipedia has numbers for Linux and various Windows versions but not macOS: https://en.wikipedia.org/wiki/Ephemeral_port

So does that mean typical desktop usage, like email, web browsing, SSH, etc. would be unaffected? Anyone have any insight on this? I'm not a networking expert myself.

I can't believe the claim that "everything else dies" when that goes directly against observed reality.

frongt@lemmy.zip · 3 pts · 129d

Ephemeral ports are used most often for outgoing traffic. Like if you connect to HTTP, the remote port is 80, but the local port could be any TCP port in the ephemeral range.

homes@piefed.world · 4 pts · 130d (2 replies)

Yeah, I run a macOS server (on 10.13.6 no less) that regularly has several months of uptime without issue, and I ran my new MacBook Pro for six months since I bought it perfectly fine without rebooting it until a recent update forced me to. I’m not sure what the problem here is.

warbosstodd@piefed.social · 6 pts · 130d (1 reply)

there may be some “secret sauce” here that combines a certain version of OS, hardware and DHCP. I thought it was an interesting read and thought I would share.

homes@piefed.world · 2 pts · 130d

I suppose it is interesting, and I wasn’t complaining about you posting it. I was more a bit puzzled about the somewhat grandiose claims that the headline makes. That’s on the author, not on you.

Zerot@fedia.io · 2 pts · 130d (2 replies)

Because it's not a security issue? It is a bug that would affect long running MacOS machines which is quite low impact.

vk6flab@lemmy.radio · 2 pts · 130d (1 reply)

CVE: Common Vulnerabilities and Exposures

ilinamorato@lemmy.world · 1 pts · 129d

Not a vulnerability or exposure. There's no threat vector here.

Tarambor@lemmy.world · 20 pts · 130d (2 replies)

AI generated crap. Lots of people posting in /r/Apple that they've uptimes many times longer than this without any issue.

nocturne@slrpnk.net · 11 pts · 130d (1 reply)

I would have to double check my Mac, but my uptime is well over this. Probably around 3 months.

mybuttnolie@sopuli.xyz · 4 pts · 130d

i have a macbook pro at work and before the update a couple days ago the last time i had rebooted it was also at least 3 months ago

tophneal@sh.itjust.works · 9 pts · 130d (2 replies)

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.

mushroommunk@lemmy.today · 5 pts · 130d (1 reply)

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.

tophneal@sh.itjust.works · 2 pts · 130d

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.

Treczoks@lemmy.world · 7 pts · 129d (3 replies)

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...

Aatube@lemmy.dbzer0.com · 3 pts · 128d (2 replies)

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.

Treczoks@lemmy.world · 2 pts · 128d (1 reply)

Amazing that nobody so far noticed the similarities to the WinNT bug of old.

Aatube@lemmy.dbzer0.com · 2 pts · 127d

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

rbos@lemmy.ca · 6 pts · 129d (1 reply)

Didn't windows XP have a similar bug? Related to the windows uptime counter, iirc.

toddestan@lemmy.world · 7 pts · 129d

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.

MonkderVierte@lemmy.zip · 5 pts · 130d

Man, the headline.

Brewchin@lemmy.world · 5 pts · 129d (2 replies)

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.

fallaciousBasis@lemmy.world · 0 pts · 129d (1 reply)

That's not a thing.

At 49.7 days a timer overflows. That could cause problems... It doesn't guarantee problems.

Brewchin@lemmy.world · 3 pts · 129d

That's the one. And fair enough.

Had a couple of users tell me it crashed their PCs, but that was my only reference.