We have observed for a few months that the Instruments tool in Xcode does not show correct memory allocation for the PacketTunnelProvider process on iOS 17. The memory allocation does not exceed 6-7 MB, which is not the case with iOS 16 or 15. Additionally, Instruments crashes the PacketTunnelProvider process after profiling for a few minutes.
Please note that I am not running Xcode in debugger mode for the PacketTunnelProvider process along with instruments, as this is a known issue that causes the PacketTunnelProvider to be killed when both Instruments and the Xcode debugger are running.
Is anyone else facing this issue and have a workaround?
gaursaransh
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Post
Replies
Boosts
Views
Activity
I have noticed a specific behavior when the Always-On VPN (AOVPN) is active in iOS. It seems that there is an issue with attaching a control filter profile, which results in no control filter running with AOVPN. It's worth noting that AOVPN blocks internet traffic if disconnected. However, when using other VPN types, the control filter profile successfully attaches and receives callbacks in the filterContentProvider network extension.
are there any constraints imposed by the Apple architecture that prevent the attachment of the filterContentProvider network extension specifically when AOVPN is running?