@Gualtier Malde
thx for answer.
What if it doesn't matter for my case, that system can terminate NSE process? just imagine, web socket aliving 10 minutes, during this, I send/receive messages via socket, after 10 min, system decide to terminate NSE, okay, but I will just receive new PN and new NSE process will start again, and new socket connection get opened, so, my connection time won't limit with 30 sec, it will limit on system decision, that, I think, will be longer than 30 sec
elaits
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 just removed some stacktrace, anyway, we can see next lines above:
Event: cpu usage Action taken: Process killed CPU: 9 seconds cpu time over 10 seconds (91% cpu average), exceeding limit of 60% cpu over 15 seconds CPU limit: 9s
As i understand, it mean that my app taking so much resources, and iOS kill app, I am right?