NEPacketTunnelProvider causes very high energy impact in main app
NEPacketTunnelProvider causes very high energy impact in main app
- Subject: NEPacketTunnelProvider causes very high energy impact in main app
- From: Neil Alexander via Macnetworkprog <email@hidden>
- Date: Mon, 14 Jun 2021 09:03:28 +0000
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=neilalexander.eu; dmarc=pass action=none header.from=neilalexander.eu; dkim=pass header.d=neilalexander.eu; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=rFBJdEFd4UM61MYM6Wf8pc/NtkpKUu2n3UouquXZT60=; b=RnUt3eX6WyF8qNAh8dmEUifObp376n3WLp99nt8tuqp/GAp4BlJZwGlJ40+55+yflNwaOtb8GXGaQRNQ4+nDT2BLGukvalqus865S0J6QuTTzsc6ia7wGyxhVRbhijCCZWwJ2e+bgeF2Dpt3eKJW97sVcswg72WS9mauYsOncYhuDVCg55uhYx9oNwk03ZNqraMTok/QzvW4iBgLo7ZZQ0H70o5DenN2rofs932dTREBDgM0rrLgJPSCc34yqlEdKnP+xiRU3rfe5GTEdOnAPjuJVnhxxyzNIXT22MY0guunDLfZl57lojT443EzpHWocY9gbwTWcVg4K6RvLo1OUQ==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=DOwyJzzLYBO+ORzifuBSo00nFjiQ+nD2L/pQ2JYVOfx1jkfYelsVOs1pMbPer+AHOFr8T7uVJBT84cMW9F6lB+lvQDBSJjAW/aY/dESEKo4K9chOxeo5V5a85VFabEycnQJcPtLyR++PzQ9VxnBfqUHQkv+FRUyPcNwnLfII04U+wAg4aKxb0Yu/+v6ARxHoD8qX6aqEYTIufMvyyHmsC7SxwX1MxQ1afxpx110yx/k88nLmdrjqHzuxYMEpMCvwX3557dzi1Lz4gHB/HL2df10TiTwMG3ifM7P3H98JKGGmL3onNF+8s4J8bwwMCE/P/WlkzCLnpEaT3plFYfeNxQ==
- Thread-topic: NEPacketTunnelProvider causes very high energy impact in main app
Hi all,
I'm observing some strange behaviour in an iOS app that implements
NEPacketTunnelExtension. I have been experiencing this for a good while now
over various different iOS versions and have never been able to get to the
bottom of it.
The moment the NEPacketTunnelProvider is started, my main app UI process starts
getting hammered with 45% "Overhead" and 25% "Network" in the Xcode Energy
Impact view and the device starts to run quite warm. CPU usage of the process
is virtually zero, network activity generated by our app is virtually
non-existent at the time (and Instruments supports this) and not aware of
anything else going on.
We do send XPC requests to the VPN extension once every couple of seconds for a
status update, but the UI has no other networking code. If we stop the VPN
extension, the "Overheads" and "Network" energy impacts of the main app drop
back down to normal. It's happening reliably and repeatably.
If we attach the debugger to the actual network extension PID, it looks
completely normal — no high energy impact there, which makes me think this
isn't being caused by our VPN extension itself. If the main app goes into the
background, it gets suspended, as expected, and the VPN extension carries on
with a comparatively low energy impact, as expected.
Having a hard time narrowing down what is going on here.
Any ideas?
Neil
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden