A macOS bug that causes TCP networking to stop working after 49.7 days

loloquwowndueo

lol reminds me of the windows 95 crash bug after 49.7 days. Have we learned nothing. https://pipiscrew.github.io/posts/why-window/

beanjuiceII

i'm on sequoia M1 laptop with uptime 16:38 up 228 days, 21:03, 1 user, load averages: 6.14 5.93 5.64 guess i'm marked safe!

otterley

Sounds like it affects every open TCP connection, not just OpenClaw. (It's pretty rare for a TCP connection to live that long, though.)

throw03172019

I only have 11 days left until my machine crashes and I lose all of my tabs.

dvh

Exactly like arduino

gghootch

What does this have to do with OpenClaw exactly?

daveorzach

If you want to see exactly when your machine will hit this, I threw together a fish shell function that calculates the precise timestamp, mostly vibe coded. calc_tcp_overflow_time.fish: https://gist.github.com/daveorzach/64538f82a89fa24e5d134557c... monitor_tcp_time_wait.fish: https://gist.github.com/daveorzach/0964a7a67c08c50043ff707cf...

WesolyKubeczek

In case of OpenClaw, this is a feature.

MatMercer

This made me remember some folks that are "I never reboot my MacOS and it's fine!". Yeah probably it is but I'll never trust any computer without periodic reboots lol.

Philpax

Ctrl+F "OpenClaw". No results. Que?

cute_boi

too much words and text for simple thing..... probably written by openclaw

jijji

I thought Alan Cox fixed all the TCP IP bugs in the early 1990s lol

awithrow

A ticking time bomb? What an overly dramatic way to talk about a bug that requires a reboot. Its not even a hard crash.

mcculley

> It will not be caught in development testing — who runs a test for 50 days? You don't have to run the system for 50 days. You can simulate the environment and tick the clock faster. Many high reliability systems are tested this way.

tjohns

Does anybody else find these AI-authored blog posts difficult to read? Something about the writing style and structure just feels unnatural, it's hard put my finger on it. At the very least, the writing takes way too long to get to a point.

justinfrankel

have multiple macOS machines with 600-1000+ day uptimes, which do TCP connections every minute or so at a minimum, they are still expiring their TIME_WAIT connections as normal. these kernel versions: Darwin Kernel Version 20.6.0: Thu Jul 6 22:12:47 PDT 2023; root:xnu-7195.141.49.702.12~1/RELEASE_ARM64_T8101 arm64 Darwin Kernel Version 17.7.0: Wed Apr 24 21:17:24 PDT 2019; root:xnu-4570.71.45~1/RELEASE_X86_64 x86_64 so... wonder what that's about?

EdNutting

I got tired of the AI writing before finding out if they even attempted to contact Apple about this issue? Does anyone know? Also, massively over-dramatised. Yes, a bug worth finding and knowing about, but it’s not a time bomb - very few users are likely to be affected by this. Knowing the nature of OS kernels, I’m guessing even just putting a Mac laptop to sleep would be enough to avoid this issue as it would reset the TCP stack - which may be why some people are reporting much longer uptimes without hitting this problem, since (iirc) uptime doesn’t reset on Macs just for a sleep? Only for a full reboot? Anyway, all in all, yeah hopefully Apple fix this but it’s not something anyone needs to panic about.

apatheticonion

Ignoring the AI article contents. God I wish Apple offered first party support for Linux on Mac computers.

poppafuze

https://news.ycombinator.com/item?id=41939318

fortran77

Nobody keeps their Macs running for more than 49.7 days? We have Windows Servers here (with long-term TCP/IP connections) that are only rebooted every 6 months to apply patches.