The Lulu download page says

"Apple also broke many aspects of networking in macOS 15 (Sequoia). Until Apple releases a fix, the solution for now appears to be to disable the macOS firewall."

Presumably doing that would likely also work around the problem for littlesnitch?

You don’t need to do anything special to “reveal” that Apple doesn’t prioritize backwards compatibility. That is very well known. For example, standard practice for audio professionals is to wait a year or more to upgrade MacOS, to give all the vendors a chance to fix what broke.

Funnily enough, that’s what the UNIX™ certification is, in some—much too limited for your purposes—sense :) See also Raymond Chen’s story of buying one of everything[1].

[1] https://devblogs.microsoft.com/oldnewthing/20050824-11/?p=34...

Eh, I agree in a sense, but I'm also ok without the same level of backwards compatibility that Windows is beleaguered by. Every new version of Windows is little more than a thin veneer of whatever they think is a popular choice for UI design that year, and with that comes a clumsy amalgamation of hugely varying settings dialogs, the classic registry, all the goop. Meanwhile on macos, I don't expect very complex software to maintain perfect compatibility, but I can reasonably expect most of the stuff I use to carry forward 5+ years. Parallels and Omnifocus were the exceptions, but 1password from 2012 is still kicking, Data Rescue 3 somehow still works, I'm sure even Adobe CS6 would even though it's from the Carbon era.

Just as well, although I loathe some of the choices Apple's made over the years, such as it's own Settings app, the overall UI would be pretty recognizable if me from 20 years ago found a time machine (pun intended). I recently bought a new mac, and it occurred to me that it feels basically like the E-Mac I used in middle school all those years ago, albeit with the occasional annoyance I wouldn't have been aware of then.

The Android CTS is essentially this for device OEMs. https://source.android.com/docs/compatibility/cts – it's a set of tests that a customised Android implementation must pass.

Huh? In service of what? There’s not all that much inherently good about backwards compatibility, but you’re really implying that deprioritising it is a misdeed. If I wanted to use an OS that prioritised backwards compatibility more than macOS, I’d use Windows, and suffer through the downsides of that trade-off. I’m happy using an OS that balances things in a way that’s more in line with my priorities.

brett@algol  minikube / default  ~/Documents/misc  sudo leaks at.obdev.littlesnitch.networkextension | grep "total leaked bytes" Password: Process 43619 is not debuggable. Due to security restrictions, leaks can only show or save contents of readonly memory of restricted processes.

Process 43619: 2194911 leaks for 6742615664 total leaked bytes.

jesus.

Definitely: They do try to avoid breaking their own first-party apps. Now third-party apps...

Damn if only they told us yesterday before I restarted for the first time in a month. I wonder how big my memory leak would have been. I have only been online for about 11 hours (~9 of those were in hibernation) now and already at a 13MB leak.

I reported that to them and at least based on the interaction they have no idea for last few months. I just have to restart them or the whole MacBook Air from time to time. I suspect it is not their issue lately as I saw others have this issues. Well … now I know. Or may be I just guess.

Yeah, I stopped using it because of that.

Same for me! On my laptop, Safari will eventually stop loading web pages after a few days of uptime, guaranteed, until I reboot. I hadn't had that on my Mac Studio, but it has much more RAM to endure the leakage longer.

I generally don't sleep my macOS machines these days, as hardware has gotten faster and faster, the pain of booting up is less and less. Unless I want to be able to wake on network etc., at least.

Apple's frameworks must be perpetually in beta.

Must be all that Swift goodness they impose on us… ;)

> For the time being, until Apple fixes this serious bug in macOS, we therefore highly recommend to turn off the built-in firewall of macOS when also using Little Snitch or Little Snitch Mini.

I remember back in the day when installing two firewalls or two antivirus programs on Windows would break it, so it will have to be reinstalled. That was 20 years ago, though, one would think we're better at making an OS by now.

Afaik the macOS port of OpenBSD's pf firewall is the only firewall used by both Apple's system settings and obdev's LittleSnitch. They're both GUI frontends to the same backend, but Apple supposedly also added internal "escape hatches" to their PF port because they couldn't be arsed to write/generate a proper ruleset with anchors to hook into.

The cynic in me assumes it's just teams from different silos trampling over each other in a shared code base. Given Apple's obsession with leak prevention they're probably prohibited by NDA from talking to each other.

I think this is the one that broke Time Machine for everyone with a third-party firewall wall

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

Not entirely sure you are upset when people do exactly what Apple has been telling everyone to do for years if they want their bug fixed

A memory leak is essentially when a program uses more and more memory because it loses track of some of it so it can't give it back to the OS. You're thinking of another kind of leak.