too much words and text for simple thing..... probably written by openclaw
A macOS bug that causes TCP networking to stop working after 49.7 days
21–30 of 120 posts
Re: A macOS bug that causes TCP networking to stop working after 49.7 days
#22In case of OpenClaw, this is a feature.
When some Russians do a prompt injection and OpenClaw is threatening to send your NSFW pics to Grandma unless you give it some Bitcoin all you have to do is drag out the negotiations for 49 days!
Re: A macOS bug that causes TCP networking to stop working after 49.7 days
#23Re: A macOS bug that causes TCP networking to stop working after 49.7 days
#24I thought Alan Cox fixed all the TCP IP bugs in the early 1990s lol
Re: A macOS bug that causes TCP networking to stop working after 49.7 days
#25A ticking time bomb? What an overly dramatic way to talk about a bug that requires a reboot. Its not even a hard crash.
Re: A macOS bug that causes TCP networking to stop working after 49.7 days
#26> 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.
Re: A macOS bug that causes TCP networking to stop working after 49.7 days
#27Sounds like it affects every open TCP connection, not just OpenClaw. (It's pretty rare for a TCP connection to live that long, though.)
Individual TCP connections don't need to live that long. Once a macOS system reaches 49.7 days of uptime, this bug starts affecting all TCP connections.
> Once a macOS system reaches 49.7 days of uptime, this bug starts affecting all TCP connections.
Current `uptime` on my work MacBook (macOS 15.7.4):
17:14 up 50 days, 22 mins, 16 users, load averages: 2.06 1.95 1.94
My personal iMac is at 279 days of uptime.
Re: A macOS bug that causes TCP networking to stop working after 49.7 days
#28lol reminds me of the windows 95 crash bug after 49.7 days. Have we learned nothing. https://pipiscrew.github.io/posts/why-window/
probably same thing for boeing 787 jets - https://www.theregister.com/2020/04/02/boeing_787_power_cycl...
says 51 days, which would be an interesting number of (milli)seconds
Re: A macOS bug that causes TCP networking to stop working after 49.7 days
#29> 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.
Heck, many video games are tested this way.
Re: A macOS bug that causes TCP networking to stop working after 49.7 days
#30This 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.
I’m still at where when I connect external hard drive or SSD via USB, use it and then eject it, I shut down the MacBook Pro completely before I unplug the USB cable. Just in case.
The longest uptime I have had on any of my recent laptops is probably around 90 days but that’s because that laptop was sitting in my garage with wall power connected (probably bad for the battery) and some external storage connected and I’d remote into that machine over WireGuard now and then. When I did reboot that machine it was only out of habit that I accidentally clicked on reboot via a remote graphical session.
Most of the time my remote use of the laptop in the garage would be ssh sessions, but occasionally I’d use Remote Desktop. Right after I clicked reboot in the Remote Desktop session I realized what mistake I had just done - I have WireGuard set up to start after login. So after the reboot, I was temporarily unable to get back in. As I was in another country I couldn’t just walk over to the garage. But I do have family that could, so I instructed one of them over the phone on how to log in for me so that WireGuard would automatically start back up. You’d think this would happen only once, but I probably had to send family to the garage on my behalf maybe three or four times after me having made the same mistake again.
For the laptops that I actually carry around and plug and unplug things to etc, normal amount of time between reboots for me is somewhere between every 1 and 3 days. Cold boot is plenty fast anyway, so shutting it down after a day of work or when ejecting an external HDD or SSD doesn’t really cost me any noticeable amount of time.