my app got a critical crash since apple releases 10.3.0 version. Here the crash log. Does anyone have any idea about this? Thanks
Related
I am getting some crash reports as following on Firebase Crashlytics. Unable to reproduce from our side. Is there any way to check this crash? or any reason?
enter image description here
enter image description here
My app encountered this crash in recent months.From the stacktrace as the following, I can‘t find any clue.This crash only happened on iOS 11.2.x and background thread. This bug almost happened only once on each user's device. I don't know if it is a bug from Apple.Can anybody give me some clues about this bug? Thanks a lot!
My app encountered this crash in recent months.From the stacktrace as the following, I can‘t find any clue.This crash only happened on iOS 11.2.x and background thread. This bug almost happened only once on each user's device. I don't know if it is a bug from Apple.Can anybody give me some clues about this bug? Thanks a lot!
here is the stacktrace:
here is the device info for the bug:
Crittercism SDK 4.3.7 is crashing in iOS 8.0 :
Getting error at com.apple.NSURLConnectionLoader after running application.
Can anybody have solution for this or need to wait for new version of SDK with fix for this bug.
Let's try doing this and see where it takes us.
Set NSZombieEnabled, MallocStackLogging, and guard malloc in the debugger. Then, when your App crashes, type this in the gdb console:
(gdb) info malloc-history 0x543216
Replace 0x543216 with the address of the object that caused the crash, and you will get a much more useful stack trace and it should help you pinpoint the exact line in your code that is causing the problem.
More can be read here: "Thread 6 com.apple.NSURLConnectionLoader: Program received signal: EXC_BAD_ACCESS"
FYI we'll be working on tying up any iOS8 related loose ends on the 17th.
Thanks for using Crittercism!
I'm getting a number of crashes in __handleUncaughtException -> CFNumberCreate -> malloc_zone_malloc (see screenshot of crash log from Crashlytics).
Can anyone explain what might be causing this?
Most likely the crash is not caused by anything related to NSNumber or CFNumber, but is caused by messing up memory earlier, and the crash you get is just the symptom.
Google for "iOS debug memory corruption" which should give you some hints.