Re: Networking framework crash
Re: Networking framework crash
- Subject: Re: Networking framework crash
- From: Michael Crawford <email@hidden>
- Date: Wed, 04 Feb 2015 19:12:03 -0800
> No disrespect, but after 30+ years of developing, I am roughly conversant with debugging strategies.
My apologies, I sent my spam before noting who I was sending it to.
Of course I know you've been a coder, actually for quite a longer time
than I have.
There are some other considerations that you might not have looked into though.
Does this happen on just one machine? If that's the case perhaps it
could be a hardware problem. Try installing MemtestOSX, rebooting as
single-user then:
$ ./memtest all 1
Let the tests run to completion. Note that this will also indirectly
test for problems with your CPU, memory controller and motherboard.
Is your box overheating? If so the fans will make a lot of noise.
Perhaps you found a bug in the kernel or one of the userspace
frameworks. I won't insult you by telling you how to regress that but
if it is in the kernel I have some insight into kernel debugging.
Cheers,
Mike
Michael David Crawford, Consulting Software Engineer
email@hidden
http://www.warplife.com/mdc/
Available for Software Development in the Portland, Oregon Metropolitan
Area.
On Wed, Feb 4, 2015 at 7:04 PM, Graham Cox <email@hidden> wrote:
>
>> On 5 Feb 2015, at 1:53 pm, Michael Crawford <email@hidden> 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 (email@hidden)
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:
This email sent to email@hidden