On 14 Feb 2017, at 17:13, Jens Alfke <[email protected]> wrote: > Then I’m back to the question of why this problem is occurring.
I’ve no idea. Honestly, it sounds like a bug, but it’s hard to be sure without an in-depth look. Is the stream scheduled via a run loop? Or a queue? If it’s a run loop, are you sure that the only code touching the stream is running on that run loop? Similarly if you’re using a queue? Did this problem happen on earlier versions of macOS? Have you enabled TLS on the socket stream? Anything interesting in the CFNetwork diagnostic log? If, when things get stuck, you force the app to do a read, does it actually get data? Share and Enjoy -- Quinn "The Eskimo!" <http://www.apple.com/developer/> Apple Developer Relations, Developer Technical Support, Core OS/Hardware _______________________________________________ Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/macnetworkprog/archive%40mail-archive.com This email sent to [email protected]
