I've recently started getting these crashes frequently. But unable to figure out what does it really mean. It seems like the crash occured in MintRequestWorker. But this log is insufficient to know about it.
I am using AFNetworking, Splunk Mint, Crashlytics, Google Analytics.
Can someone guide me what am I probably doing wrong here?
Thread : Crashed: com.apple.root.default-priority
0 IOKit 0x30bc831c IOServiceAddInterestNotification + 47
1 UIKit 0x32950af1 _MatchedBatteries + 76
2 UIKit 0x32950af1 _MatchedBatteries + 76
3 UIKit 0x32950a2f -[UIDevice setBatteryMonitoringEnabled:] + 198
4 Earthmiles 0x001a268f -[DataFixture appendBaseValues] + 1652367
5 Earthmiles 0x001a1f53 -[DataFixture init] + 1650515
6 Earthmiles 0x001ce939 -[EventDataFixture init] + 1833273
7 Earthmiles 0x001ca657 +[GnipDataFixture getInstanceWithAppEnvironment:] + 1816151
8 Earthmiles 0x001db0e9 -[MintRequestJsonSerializer serializeEventToJsonForGnipWithAppEnvironment:] + 1884393
9 Earthmiles 0x001a964d -[MintRequestWorker logEvent:] + 1680973
10 Earthmiles 0x001ab19b -[MintRequestWorker closeSession] + 1687963
11 Earthmiles 0x001ab51d __58-[MintRequestWorker closeSessionAsyncWithCompletionBlock:]_block_invoke + 1688861
12 libdispatch.dylib 0x3ab5bd53 _dispatch_call_block_and_release + 10
13 libdispatch.dylib 0x3ab61689 _dispatch_root_queue_drain + 228
14 libdispatch.dylib 0x3ab618dd _dispatch_worker_thread2 + 56
15 libsystem_pthread.dylib 0x3ac8cc17 _pthread_wqthread + 298
16 libsystem_pthread.dylib 0x3ac8cadc start_wqthread + 8
Related
We have been facing a weird crash from core data from long time and haven't found anything what to do. Below is the crash stack to get more insight on it. It is a production issue and not replicate at our end.
Crashed: NSManagedObjectContext 0x2810fd450
0 CoreData 0x6f8d8 _PFObjectIDFastHash64 + 40
1 CoreFoundation 0xef54 __CFBasicHashRehash + 948
2 CoreFoundation 0xe76c CFBasicHashRemoveValue + 2412
3 CoreFoundation 0x45ce0 CFDictionaryRemoveValue + 336
4 CoreData 0x10781c -[NSManagedObjectContext(_NSInternalAdditions) _forgetObject:propagateToObjectStore:removeFromRegistry:] + 132
5 CoreData 0x29554 -[_PFManagedObjectReferenceQueue _processReferenceQueue:] + 916
6 CoreData 0xa284c __90-[NSManagedObjectContext(_NSInternalNotificationHandling) _registerAsyncReferenceCallback]_block_invoke + 80
7 CoreData 0x1f754 developerSubmittedBlockToNSManagedObjectContextPerform + 156
8 libdispatch.dylib 0x4660 _dispatch_client_callout + 20
9 libdispatch.dylib 0xbde4 _dispatch_lane_serial_drain + 672
10 libdispatch.dylib 0xc958 _dispatch_lane_invoke + 392
11 libdispatch.dylib 0x171a8 _dispatch_workloop_worker_thread + 656
12 libsystem_pthread.dylib 0x10f4 _pthread_wqthread + 288
13 libsystem_pthread.dylib 0xe94 start_wqthread + 8
Looks like the problem could be in NSManagedObjectContext performing some work. Maybe integrating some data-collection lib, as Crashlytics can help.
Regarding stack trace: could you please send the original error message (as shown on screenshot)?.
For now I can draw only bare suggestions that are not so relevant.
After new iOS release in our app become crashing with PHCompositeMediaResult. What I see in Crashlytics.
[PHCompositeMediaResult isPlaceholder]
[PHCompositeMediaResult isDegraded]
[PHCompositeMediaResult isCancelled]
Any idea what can we do with this?
Edit
Stacktrace:
Crashed: com.apple.photos.imageManagerCache
0 libobjc.A.dylib 0x1b12b8190 objc_msgSend + 16
1 CoreFoundation 0x1b146ec04 -[__NSDictionaryM objectForKeyedSubscript:] + 180
2 Photos 0x1bc7f385c -[PHCompositeMediaResult isPlaceholder] + 36
3 Photos 0x1bc84b978 -[PHCachingImageManager _canPopulateCacheForResult:] + 56
4 Photos 0x1bc84e588 __90-[PHCachingImageManager additionalWorkForImageRequestCompletedWithResult:request:context:]_block_invoke + 64
5 libdispatch.dylib 0x1b1260658 _dispatch_call_block_and_release + 24
6 libdispatch.dylib 0x1b12611cc _dispatch_client_callout + 16
7 libdispatch.dylib 0x1b120d524 _dispatch_lane_serial_drain$VARIANT$mp + 608
8 libdispatch.dylib 0x1b120df18 _dispatch_lane_invoke$VARIANT$mp + 420
9 libdispatch.dylib 0x1b1217400 _dispatch_workloop_worker_thread + 588
10 libsystem_pthread.dylib 0x1b12b0fa8 _pthread_wqthread + 276
11 libsystem_pthread.dylib 0x1b12b3ae4 start_wqthread + 8
This appears to just happen in iOS 13.0.0. I don't have any instances of it happening on 13.1, 13.1.1, or 13.1.2... So it was probably a bug in the OS that they quickly figured out and fixed. Hopefully not many users stay on 13.0.0 for long. Maybe the "what to do about this?" answer is just to do nothing.
My iOS app had a crash caused by CFNetwork. I cannot reproduce it. The app was running on iOS 12. I am using Alamofire to perform HTTP requests, but I don't think it was caused by Alamofire. Anyone has any idea?
Crashed: com.apple.CFNetwork.Connection
0 libsystem_kernel.dylib 0x1ba289104 __pthread_kill + 8
1 libsystem_pthread.dylib 0x1ba308a00 pthread_kill$VARIANT$armv81 + 296
2 libsystem_c.dylib 0x1ba1e0d78 abort + 140
3 libsystem_c.dylib 0x1ba1ae67c basename_r + 314
4 CFNetwork 0x1bae63478 invocation function for block in TCPIOConnection::_tlsValidateServerTrust(nw_tls_context*) + 346
5 CFNetwork 0x1bae614e0 TCPIOConnection::_handleTLSEvent(nw_tls_context*, tls_handshake_message_t, void () block_pointer, bool) + 720
6 libnetwork.dylib 0x1bb8716b0 __tcp_connection_set_tls_message_handler_on_nw_connection_block_invoke + 168
7 libboringssl.dylib 0x1bb5e505c __boringssl_context_issue_tls_handshake_callback_block_invoke + 188
8 libdispatch.dylib 0x1ba12b6c8 _dispatch_call_block_and_release + 24
9 libdispatch.dylib 0x1ba12c484 _dispatch_client_callout + 16
10 libdispatch.dylib 0x1ba106fb0 _dispatch_lane_serial_drain$VARIANT$armv81 + 548
11 libdispatch.dylib 0x1ba107b2c _dispatch_lane_invoke$VARIANT$armv81 + 468
12 libdispatch.dylib 0x1ba108d70 _dispatch_workloop_invoke$VARIANT$armv81 + 1892
13 libdispatch.dylib 0x1ba10ff14 _dispatch_workloop_worker_thread + 584
14 libsystem_pthread.dylib 0x1ba30e0f0 _pthread_wqthread + 312
15 libsystem_pthread.dylib 0x1ba310d00 start_wqthread + 4
Some users are reporting crashes in my app when I checked it from crittercism. It is giving me below stack trace. I have update my core data with new model version( Using light weight migration). I am using Restkit and Magical Records in my app. I didn't get what is the problem ?
>>0 libobjc.A.dylib 0x353a16ba objc_retain + 8
! 1 Provider 0x00aeb701 __78-[RKManagedObjectRequestOperation obtainPermanentObjectIDsForInsertedObjects:]_block_invoke (RKManagedObjectRequestOperation.m:885)
2 CoreData 0x26c7496b developerSubmittedBlockToNSManagedObjectContextPerform + 180
3 libdispatch.dylib 0x35917c6f _dispatch_client_callout + 20
4 libdispatch.dylib 0x35921559 _dispatch_barrier_sync_f_invoke + 46
5 CoreData 0x26c74857 -[NSManagedObjectContext performBlockAndWait:] + 200
6 Provider 0x00aeb555 -[RKManagedObjectRequestOperation obtainPermanentObjectIDsForInsertedObjects:] (RKManagedObjectRequestOperation.m:882)
7 Provider 0x00ae8c67 __79-[RKManagedObjectRequestOperation performMappingOnResponseWithCompletionBlock:]_block_invoke348 (RKManagedObjectRequestOperation.m:645)
8 Provider 0x00b15961 -[RKResponseMapperOperation willFinish] (RKResponseMapperOperation.m:325)
9 Provider 0x00b1609d -[RKResponseMapperOperation main] (RKResponseMapperOperation.m:412)
10 Foundation 0x27b7cb0d -[__NSOperationInternal _start:] + 766
11 Foundation 0x27c21d93 __NSOQSchedule_f + 184
12 libdispatch.dylib 0x359224d3 _dispatch_queue_drain$VARIANT$mp + 1460
13 libdispatch.dylib 0x35921da1 _dispatch_queue_invoke$VARIANT$mp + 82
14 libdispatch.dylib 0x35924491 _dispatch_root_queue_drain + 386
15 libdispatch.dylib 0x359258a3 _dispatch_worker_thread3 + 104
16 libsystem_pthread.dylib 0x35a99d9d _pthread_wqthread + 666
17 libsystem_pthread.dylib 0x35a99af0 start_wqthread + 6
With the release of iOS 8 we've started getting several types of crashes that we've never seen before. Wondering if anyone else has seen this or has any suggestions.
Several of them look similar to this:
Thread : Crashed: com.apple.NSURLSession-work
0 libsystem_kernel.dylib 0x2fd3adfc __pthread_kill + 8
1 libsystem_pthread.dylib 0x2fdb8d37 pthread_kill + 62
2 libsystem_c.dylib 0x2fcda909 abort + 76
3 libsystem_malloc.dylib 0x2fd6b3af szone_error + 334
4 libsystem_malloc.dylib 0x2fd6b637 free_small_botch + 66
5 CFNetwork 0x21a63935 HTTPMessage::ensureParserFinished() + 72
6 CFNetwork 0x21a7aad3 HTTPMessage::copyHeaderFieldValue(__CFString const*) + 18
7 CFNetwork 0x21b43e87 HTTPSniffing::checkRequestAndUpdateResponseForSniffingPurposes(_CFURLRequest const*, _CFURLResponse*) + 130
8 CFNetwork 0x21b15ddd URLConnectionClient::_loaderClientEvent_DidReceiveResponse(_CFURLResponse*) + 340
9 CFNetwork 0x21b1b7d9 ___ZN19URLConnectionLoader26protocolDidReceiveResponseEP14_CFURLResponse_block_invoke + 24
10 CFNetwork 0x21ac9e03 ___ZN20ClassicURLConnection21withLoaderClientAsyncEU13block_pointerFvP21LoaderClientInterfaceE_block_invoke + 14
11 CFNetwork 0x21b14ca9 ___ZNK25URLConnectionInstanceData18withWorkQueueAsyncEU13block_pointerFvvE_block_invoke + 12
12 libdispatch.dylib 0x2fc548cb _dispatch_call_block_and_release + 10
13 libdispatch.dylib 0x2fc5c651 _dispatch_queue_drain + 952
14 libdispatch.dylib 0x2fc5709d _dispatch_queue_invoke + 84
15 libdispatch.dylib 0x2fc5dba1 _dispatch_root_queue_drain + 320
16 libdispatch.dylib 0x2fc5ecd7 _dispatch_worker_thread3 + 94
17 libsystem_pthread.dylib 0x2fdb5e31 _pthread_wqthread + 668
Thanks,
Dan
This is a bug in Apple's code and there is nothing you can do about it, other than wait for an iOS update (or you may want to avoid using the NSURLSession APIs and invoking -[NSURLHTTPResponse allHeaderFields]). But don't hold your horses, it's been there since at least iOS 7.0 and has been reported multiple times (I have done it and my ticket got closed as dupe) and is still not fixed on iOS 8.0.2.
Try updating to the latest AFNetworking 2.5.3.