Possible 26.2 memory leak regression in Network, when multiple NEXT active

Hi, After the release of macOS Tahoe 26.2. We are seeing memory leaks if our Network Protection Extension is used alongside the Apple Built In Firewall, a second Security Solution that does Network Protection and a VPN. Our NEXT, socketfilterfw and the other security solution consume instead of a few MB of Memory now multiple Gigabytes of Memory. This issue started with the public release of macOS Tahoe 26.2, this issue was not present in earlier versions of macOS and the same set of Software. Just testing our solution by itself will not show this behavior. I unfortunately can't try to reproduce the issue on my test device that runs the latest 26.3 beta as I do not have the third party software installed there and I can't get it.

Our Network extension implements depending on the license and enabled features:

  • NEFilterDataProvider
  • NEDNSProxyProvider
  • NETransparentProxyProvider

For all man in the middle Use Cases we are using Network Framework, to communicate with the peers. And leaks suggest that the there is a memory leak within internals of the Network Framework.

Here is a shortened sample of the leaks output of our Network extension. However, the third party NEXT does show the same leaks. More details can be found on the Feedback with the ID FB21649104

snippet is blocking post? sensitive language 

Does anyone see similar issues or has an idea what could cause this issue, except a regression of the Network.framework introduced with macOS Tahoe 26.2?

Best Regards, Timo

Answered by DTS Engineer in 874052022

Thanks for opening a forums thread about this.

More details can be found on the Feedback with the ID FB21649104

And thanks for filing that.

Based on the analysis in that bug report, my understanding is that:

  • This is a known issue.
  • We believe it’s fixed in macOS 26.3 beta.

Please try reproducing this with the latest 26.3 beta seed and let us know how you get along.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

I couldn't post the snippet as it fails the sensitive language check... So I try to add it as text file [here]

Thanks for opening a forums thread about this.

More details can be found on the Feedback with the ID FB21649104

And thanks for filing that.

Based on the analysis in that bug report, my understanding is that:

  • This is a known issue.
  • We believe it’s fixed in macOS 26.3 beta.

Please try reproducing this with the latest 26.3 beta seed and let us know how you get along.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Short update, Beta 3 did not fix the issue unfortunately, we updated the linked Feedback accordingly.

Beta 3 did not fix the issue

Bummer.

And that’s actually quite surprising, because 26.3b3 should contain a fix for a bug that looks very similar to your bug.

we updated the linked Feedback accordingly.

Thank you.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Can you re-test on the just-seeded 26.4b1 release? There’s a similar issue (FB21376045) called out in the macOS Tahoe 26.4 Beta Release Notes notes.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Hi, It looks like the issue is fixed, or at least its impact is reduced. After leaving my MacBook running tonight it accumulated no significant amount of Memory. Still leaks is reporting some leaks. We will provide a leaks report from a device with Sequoia and obviously from the 26.4 device in the Feedback.

Best regards, Timo

Thanks for checking this. And I’m glad to hear that things are improving.

We will provide a leaks report … from the 26.4 device in the Feedback.

Thanks.

Although I think you might be better off creating a new bug for that. The current bugs were used to track the fix for the major memory issue that landed in 26.4 beta. The remaining minor leak is likely to have a different cause and thus it’s better to have a different bug.

If you do file a new bug, please post its bug number here, just for the record.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Ok I have to correct myself, after a few more hours using the MacBook and switching networks the Memory utilization increased again. Our NEXT is now at 1.8GB and socketfilterfw is at 1.2GB. It seems to be slower but there is still a leak.

the Memory utilization increased again.

Bummer.

But my previous advice still holds: If you continue to have problems with this on 26.4b1, it’s best to file a new bug with the details.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Possible 26.2 memory leak regression in Network, when multiple NEXT active
 
 
Q