> On 5 Feb 2015, at 1:53 pm, Michael Crawford <mdcrawf...@gmail.com> wrote: > > This Spam Has Been Brought To You By:
No disrespect, but after 30+ years of developing, I am roughly conversant with debugging strategies. This is not an easy one to isolate, because there's very little information on EXC_GUARD that I can find, the code is being run on a thread I didn't create, and whose provenance (calling chain) is not directly related to my high-level code (NSURLSession/NSURLSessionDataTask). It's also only just started happening in an app that has been happily running for months without a problem (notwithstanding the memory leak I discussed a couple of weeks ago that was in the same app, and also appears not to be my bug). What is new is that I may have started to hit some sort of unexpected internal limit that I hadn't previously triggered. If that's the case it may have profound implications for my app's architecture, which does create one session per task, rather than one session per app. --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
