ios - AFNetworking crash analysis for EXC_BAD_ACCESS KERN_INVALID_ADDRESS -
i'm getting crash reports of afnetworking throwing exc_bad_access kern_invalid_address:
thread : crashed: com.apple.root.default-priority 0 libobjc.a.dylib 0x39e237fa objc_release + 9 1 my_app 0x0015ba63 __64-[afhttprequestoperation setcompletionblockwithsuccess:failure:]_block_invoke (afhttprequestoperation.m:266) 2 my_app 0x00163bf7 __47-[afurlconnectionoperation setcompletionblock:]_block_invoke (afurlconnectionoperation.m:301) 3 foundation 0x3049a2a9 __103+[__nsoperationinternal _observevalueforkeypath:ofobject:changekind:oldvalue:newvalue:indexes:context:]_block_invoke96 + 12 4 libdispatch.dylib 0x3a30b0c3 _dispatch_call_block_and_release + 10 5 libdispatch.dylib 0x3a3107d9 _dispatch_root_queue_drain + 224 6 libdispatch.dylib 0x3a3109c5 _dispatch_worker_thread2 + 56 7 libsystem_pthread.dylib 0x3a43adff _pthread_wqthread + 298 i need understand possible bug. happens sometimes, rare , related timeout issue when user using 3g (network can disconnected while loading data).
i don't post code because can't find on crash log in file or class crash happened , use afnetworking in lot of files.
without code conjecture but:
something in completion block being accessed after deallocated. commonly, happens when network operation isn't cancelled after view controller dismissed.
Comments
Post a Comment