> On 5 Feb 2015, at 2:14 pm, Roland King <r...@rols.org> wrote: > >> >> >> I am googling EXC_GUARD but haven't found anything that breaks it down - >> just a bunch of people asking what it is. >> > > Really? Google sent me to twitter sent me to devforums sent me to eskimo1. eg > > https://devforums.apple.com/message/914791#914791
Yep, I found that just after I sent my previous. Interesting, though a little difficult to relate exactly to my crash. I guess tcp_connection_get_socket() creates a file handle for the socket stream (?? guessing) and that's the one tripping the EXC_GUARD. Do you or anyone else know if there's some inherent limit to the number of simultaneous sockets that can be opened? I'm supposing that there's a 1:1 correspondence between a NSURLSession and a socket, because of the description against [NSURLSession resetWithCompletionHandler:] says: "This method empties all cookies, caches and credential stores, removes disk files, flushes in-progress downloads to disk, and ensures that future requests occur on a new socket" This implies that there's a socket associated with the session. Since I have also a 1:1 correspondence between my app's individual tasks and NSURLSession, I'm opening 1 socket per task as my app starts. So around 50 in my current test situation. > if you aren’t opening your own files/creating your own filehandles I suspect > you have a bugreport in your future. > > You might also try a post in CoreOS on devforums or on the networking apple > mail list as that’s where Quinn hangs out. That sounds like a good thing to try. --Graham _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
