MacOS sometimes leaks traffic after system updates

I have never heard of anyone with this issue.

The only explanation is that you restarted whilst having the "Open All Previous Application" checkbox enabled. And yes it will launch processes after you have logged in but before the Desktop is shown.

Either that you or you have some launch daemon that is opening a browser.

I've had similar experiences with MacOS. I uncheck that goddamn box all the time and still it relaunches previously opened applications half the time. If my application or computer crashes, I don't want the crashy application to open up at startup again. MacOS isn't perfect.

I also have this issue from time to time.

> The only explanation is that [...]

Please show some more imagination.

OSX is particularly lousy with remembering user preferences and configuration. I quit using it after I grew sick of raging at it forgetting what applications want different files to open with. I've never had this sort of problem on Linux.

I had this issue, and something similar in my old iPhone. I'm sure there are other explanations, because yours is not it.

I’m very confident that it’s either this or the restore-after-crash feature that OP is seeing. I don’t think it’s anything specific to Safari, because I have never seen Safari opened before login when it’s not my default browser.

That said, there should probably be a checkbox in system settings to disable login “prewarming”.

In my experience, when filetype associations change under macOS it’s because some app I’ve used recently has made those changes without asking me.

I know some people are tired of all the prompts but I don’t think apps should be able to change those associations without first prompting the user.

Maybe you should use your imagination and read the second part of what I wrote.

Which is that it could be a launch daemon. It's very common for third party apps to use their imagination and do dumb things on startup.

I actually used Chrome and Edge. Both show that problem. But the main issue is not those browser autoplaying audio and video on "restore", even though it is an issue, its the OS thinking its OK to load apps before a user authenticated itself after boot

> Maybe you should use your imagination and read the second part of what I wrote.

The comment only advances two causes.

> Which is that it could be a launch daemon. It's very common for third party apps to use their imagination and do dumb things on startup.

Yes, that's possible, but unlikely to be an exhaustive list of reasons. Especially since in this case it's about browser tabs playing stuff before logging in, not about any weird third part apps.