this post was submitted on 09 Apr 2026
121 points (83.1% liked)

Technology

83677 readers
3922 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 2 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
121
We Found a Ticking Time Bomb in macOS TCP Networking - It Detonates After Exactly 49 Days - Photon Blog (photon.codes)
submitted 2 days ago* (last edited 2 days ago) by warbosstodd@piefed.social to c/technology@lemmy.world
37 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] Aatube@lemmy.dbzer0.com 2 points 21 hours ago (1 children)

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 points 2 hours ago (1 children)

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

[–] Aatube@lemmy.dbzer0.com 1 points 22 minutes ago

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