An app that I'm operative on has been experiencing an unequivocally rare
wreck that we am amateurish to imitate and a wholly information we have
about is it from Crashlytics. It is wholly duty on ios7 and googling
mmapFileDeallocate advantage one site where someone else was experiencing
a same wreck though their emanate went divided with an os update. Here is
a stack:Thread : Crashed: tcpConnWorkQueue0 libobjc.A.dylib
0x3aa00b36 objc_msgSend + 211 CFNetwork 0x2fece4c3
__CFURLCache::removeMMappedDataFromSet(void*) + 342 CFNetwork
0x2fecfa45 mmapFileDeallocate(void*, void*) + 243 CoreFoundation
0x3024ef5f __CFDataDeallocate + 304 CoreFoundation
0x301c75f7 CFRelease + 4625 CoreFoundation
0x3023fed5 __CFArrayReleaseValues + 2926 CoreFoundation
0x301c75f7 CFRelease + 4627 CFNetwork 0x2fe5f1d5
__CFCachedURLResponse::~__CFCachedURLResponse() + 408 CFNetwork
0x2fe5f19f __CFCachedURLResponse::~__CFCachedURLResponse() +
109 CoreFoundation 0x301c75f7 CFRelease + 46210 CFNetwork
0x2feaeda1 HTTPProtocol::~HTTPProtocol() + 73211
CoreFoundation 0x301c75f7 CFRelease + 46212 CoreFoundation
0x302b10f0 __CFBasicHashDrain + 33213 CoreFoundation
0x301c75f7 CFRelease + 46214 CFNetwork
0x2fe9226b SocketStream::~SocketStream() + 40615 CFNetwork
0x2fe920c5 SocketStream::~SocketStream() + 2016 CoreFoundation
0x301c75f7 CFRelease + 46217 libdispatch.dylib
0x3aee8d1b _dispatch_call_block_and_release + 1018 libdispatch.dylib
0x3aeef273 _dispatch_queue_drain$VARIANT$mp + 37419
libdispatch.dylib 0x3aeef06b
_dispatch_queue_invoke$VARIANT$mp + 4220 libdispatch.dylib
0x3aeefce1 _dispatch_root_queue_drain + 7621 libdispatch.dylib
0x3aeeff59 _dispatch_worker_thread2 + 5622 libsystem_pthread.dylib
0x3b02adbf _pthread_wqthread + 298I can post other threads during time of
wreck though a wholly one that stands out to me is AFNetworking though we
haven't been means to find anything identical in their issues.
No comments:
Post a Comment