I am converting an existing project to ARC. It is converting some of the variables to __unsafe_unretained.
My application is crashing with a message [CFString retain]: message sent to deallocated instance 0x7020100. As my application is huge , it is crashing with this message in every flow. Can anybody suggest a generic solution to this.
Related
When loading the main view controller of my app it loads multiple images. Using the sd_setImage(with: reference) method. It has worked forever and now I am suddenly getting crashes with the exception
-[SDImageCache storeImage:forKey:]: unrecognized selector sent to instance 0x600000c60380
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[SDImageCache storeImage:forKey:]: unrecognized selector sent to instance 0x600000c60380'
The stacktrace isn't showing a line in my code that's causing the problem. Is this an internal Firebase bug? How do I fix it?
Firebase calls continuous asynchronous calls to the observer. You should always check for nil or NSNull before attempting to present data from the database. You may have a higher resolution image that takes longer to load than it does your view to appear.
There are a lot of posts on this 'type' of error
[__NSCFNumber length]: unrecognized selector sent to instance 0xb000000000c58913
but none of it has bearing on my situation unfortunately.
The reason is our app is crashing on a background thread with the flurry SDK. I can't investigate the stack trace any deeper because I just get machine code.
I've tried commenting every line of code inside my flurry.m file but not of it encapsulates the error because this is happening inside the flurrySDK.
Its always crashing on thread 22 when I resume from background on the function
+[FlurryProtocolData limitStringLength:]
If you have any advice what so ever on how I look at this further I would love to hear it!
We were passing an ID as one of the session parameters to Flurry.
However it doesn't cause a crash until its loaded from a background thread oddly enough.r
Making sure the ID was a string before passing it fixed the issue.
I am at a complete lose here. I get this error when the page finishes loading and it only happens on the ipad. This error started happening with ios 7. How can i get the stacktrace for this memory address.
Every time a user taps the home button while my app is active, I am getting the following exception. Slight caveat - The example exception below references NSCFString. However, the type of object that gets sent this message, and thus causes the exception is totally random. It could be an NSData or an OS_dispatch_queue_specific_queue.
[__NSCFString didEnterBackground:]: unrecognized selector sent to
instance 0x155344c0 * Terminating app due to uncaught exception
'NSInvalidArgumentException', reason: '-[__NSCFString
didEnterBackground:]: unrecognized selector sent to instance
0x155344c0
Happens every single time the app is resigned active, but the object receiving the message is never the same.
I assume this is some sort of memory issue but am having trouble tracking it down. Mostly because nothing in my code ever directly sends/receives this message, or is registered to receive the UIApplicationWillResignActiveNotification. Also, there is nothing in my appDelegate for the applicationDidEnterBackground:application method.
Has anyone ever seen this type of behavior? And if so, what is the best way to debug? Or maybe another way, what sorts of objects would be automatically sent the didEnterBackground message that I am clearly mismanaging?
It sounds like you have a zombie.
A zombie is an object that gets called after it is deallocated. Often, the memory address of the object is then used for another object, so the message goes to the wrong object.
Do you have code that registers one of your application objects for a "did enter background" notification (UIApplicationDidEnterBackgroundNotification) using the method addObserver:selector:name:object:? And does that notification specify a selector of "didEnterBackground:?"
My guess is that you're registering for UIApplicationDidEnterBackgroundNotification notifications, and then the notificationObserver you're specifying is being deallocated. That would cause the exact behavior you are describing.
BTW, you might want to run your app using the zombies instrument, or turn on the NSZombies environment variable to look for zombies. Then press the home button to cause the crash and see what Xcode/instruments tells you.
This is showing up.
I'm using CoreLocation.
Googling for setLocationPingTimer doesn't show anything.
You're sending the setLocationPingTimer: message to an NSString object. Mostly likely, the object that should accept the message has been deallocated and a string happens to be in the same memory location. That's to say, you really have a memory management issue.