NEAppProxyProvider on OS X 10.11.6 goes in not responding state in Activity Monitor

Hi,


We are testing NEAppProxyProvider solution on OSX 10.11.6 and observed that in the Activity Monitor the process turns RED and shown Not Responding. Functionally it is fine and we can pass and receive traffic through this VPN connection even though process says Not Responding.


Is it beacuse somehow our process is not responding to Apple Events? How can we solve this issue and make sure that main run loop is available to Apple Events. We are not doing much on the main run loop explicitely though. Also, we do not see this issue on macOS 10.12.


Thanks and regards,

Sanjay.

Replies

Is it beacuse somehow our process is not responding to Apple Events?

Not Apple events specifically, but UI events in general. It seems that something in your packet tunnel provider has caused it to connect to the window server which is now sending it events (these aren’t necessary window events, lots of different events flow through the window server). Packet tunnel providers don’t handle such events (obviously), so they back up in the window server and you get this red status. In general this isn’t a problem, other than the fact that it’s a bit weird that you connect to the window server at all.

What frameworks does your packet tunnel provider link to? Specifically, what do you see if you run the following?

$ otool -L /path/to/your.appex

Share and Enjoy

Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

Hi ,

$ otool -L /path/to/your.appex returns:


/usr/lib/libc++.1.dylib (compatibility version 1.0.0, current version 307.5.0)

/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.8)

/System/Library/Frameworks/Security.framework/Versions/A/Security (compatibility version 1.0.0, current version 57740.51.2)

/System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration (compatibility version 1.0.0, current version 888.51.1)

/usr/lib/libresolv.9.dylib (compatibility version 1.0.0, current version 1.0.0)

/System/Library/Frameworks/Foundation.framework/Versions/C/Foundation (compatibility version 300.0.0, current version 1349.63.0)

/usr/lib/libobjc.A.dylib (compatibility version 1.0.0, current version 228.0.0)

/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1238.50.2)

/System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork (compatibility version 1.0.0, current version 811.4.18)

/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1349.64.0)

/System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices (compatibility version 1.0.0, current version 775.19.0)

/System/Library/Frameworks/NetworkExtension.framework/Versions/A/NetworkExtension (compatibility version 1.0.0, current version 1.0.0)


Thanks and regards.

Everything there looks fine. I’m not entirely sure why your provider is connecting to the window server, and only on 10.11, with just those imports. Finding out would require some in-depth debugging, and I’m not sure it’s worth the effort doing that given that this problem is pretty much cosmetic in nature.

Share and Enjoy

Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"