FXImageView
FXImageView copied to clipboard
FXImageView processImage SIGABRT
Crashlytics bug report...
10com.apple.root.default-priority Crashed 0 ... libsystem_kernel.dylib pthread_kill + 8 5 libsystem_c.dylib szone_free + 2050 6 CoreFoundation CFAllocatorDeallocate + 122 7 CFNetwork HTTPMessage::ensureParserFinished() + 46 8 CFNetwork HTTPMessage::copyHeaderFieldValue(unsigned int) + 12 9 CFNetwork URLResponse::getMIMEType() + 68 10 CFNetwork URLConnectionClient::clientDidReceiveResponse(CFURLResponse, URLConnectionClient::ClientConnectionEventQueue) + 206 11 CFNetwork URLConnectionClient::ClientConnectionEventQueue::processAllEventsAndConsumePayload(XConnectionEventInfo<XClientEvent, XClientEventParams>, long) + 442 12 CFNetwork URLConnectionClient::ClientConnectionEventQueue::processAllEventsAndConsumePayload(XConnectionEventInfo<XClientEvent, XClientEventParams>, long) + 668 13 CFNetwork URLConnectionClient::ClientConnectionEventQueue::processAllEventsAndConsumePayload(XConnectionEventInfo<XClientEvent, XClientEventParams>*, long) + 668 14 CFNetwork URLConnectionClient::processEvents() + 106 15 CFNetwork MultiplexerSource::perform() + 156 16 ... CoreFoundation __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION + 14 21 CFNetwork CFURLConnectionSendSynchronousRequest + 346 22 Foundation +[NSURLConnection sendSynchronousRequest:returningResponse:error:] + 248 23 MyApp FXImageView.m line 315 -[FXImageView processImage] 24 MyApp FXImageView.m line 64 -[FXImageOperation main] 25 Foundation -[__NSOperationInternal start] + 862 26 Foundation __block_global_6 + 102 27 ... libdispatch.dylib _dispatch_call_block_and_release + 12 29 libsystem_c.dylib _pthread_wqthread + 294
That seems to be a crash inside NSURLConnection. Unless you sent it a bad URL, this was probably caused by something unrelated like a dangling pointer or some cross-threading badness.
Do you know the circumstances? Can you reproduce it reliably? Etc.
@nicklockwood unfortunately I cannot reproduce it. I just copied it from Crashlytics.
@nicklockwood I've also got another crash from Crashlytics:
Exception Type: EXC_BAD_ACCESS Code: KERN_INVALID_ADDRESS at 0x2415919112
28NSOperation low-priority concurrency-limiting queue Crashed
0 libobjc.A.dylib objc_msgSend + 15
1 CoreFoundation CFHash + 84
2 ... CoreFoundation __CFDictionaryHashKey + 18
4 CoreFoundation __CFBasicHashRemoveValue + 524
5 CoreFoundation CFBasicHashRemoveValue + 2908
6 CoreFoundation CFDictionaryRemoveValue + 178
7 ... UIKit -[UIView dealloc] + 386
9 libobjc.A.dylib _objc_rootRelease + 36
10 UIKit -[UIView(Hierarchy) removeFromSuperview] + 182
11 ... UIKit -[UIView dealloc] + 272
13 libobjc.A.dylib _objc_rootRelease + 36
14 UIKit -[UIView(Hierarchy) removeFromSuperview] + 182
15 ... UIKit -[UIView dealloc] + 272
19 libobjc.A.dylib objc_storeStrong + 30
20 MyApp
FXImageView.m line 55
-[FXImageOperation .cxx_destruct]
21 ... libobjc.A.dylib object_cxxDestructFromClass + 56
32 libsystem_c.dylib _pthread_wqthread + 294
That looks a like a view might be getting released on a background thread. I'll see if I can identify why that might happen.
Any update on this issue ? As I am also getting the same issue
I'm not able to reproduce it, so I can't really do anything.